| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
DOC: caution against relying upon NumPy's implementation in subclasses
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I think this is an important warning to include for subclass authors.
Otherwise, we will be expanding our exposure of internal APIs as part of
``__array_function__``. All things being equal, it's great when things "just
work" subclasses, but I don't want to guarantee it. In particular, I would be
very displeased if ``__array_function__`` leads to NumPy adding more subclass
specific hacks like always calling ``mean()`` inside ``median()`` (GH-3846).
mhvk: please take a look.
|
|\ \
| |/
|/|
| |
| | |
ENH: randomgen
This merges randomgen into numpy, which was originally developed at https://github.com/bashtage/randomgen and provides a new and improved API for random number generation with much new and improved functionality.
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
remove numpy.random.gen, BRNG.generator, pcg*, rand, randn
remove use_mask and Lemire's method, fix benchmarks for PCG removal
convert brng to bitgen (in C) and bit_generator (in python)
convert base R{NG,andom.*} to BitGenerator, fix last commit
randint -> integers, remove rand, randn, random_integers
RandomGenerator -> Generator, more "basic RNG" -> BitGenerator
random_sample -> random, jump -> jumped, resync with randomgen
Remove derived code from entropy
Port over changes accepted in upstream to protect log(0.0) where relevant
fix doctests for jumped, better document choice
Remove Python 2.7 shims
Use NPY_INLINE to simplify
Fix performance.py to work
Renam directory brng to bit_generators
Fix examples wiht new directory structure
Clarify relationship to historical RandomState
Remove references to .generator
Rename xoshiro256/512starstar
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This reverts most of the changes from GH-13305, and adds a brief discussion
of ``__skip_array_function__`` into the "Alternatives" section.
We still use NumPy's implementation of the function internally inside
``ndarray.__array_function__``, but I've given it a new name in the NEP
(``_implementation``) to indicate that it's a private API.
|
|\ \ \
| |_|/
|/| | |
DOC: roadmap update
|
| | |
| | |
| | |
| | | |
[ci skip]
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- Update for changes in the past year
- Make top-level headings clearer (interoperability, extensibility, etc)
- Give website and documentation its own heading (is important)
- Remove typing and array scalars, doesn't belong here
- General cleanup, fix ReST formatting, etc.
|
| |/
|/| |
|
| | |
|
| | |
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
| |
Fix GH12974
This includes two minor changes to NEP-18 that will need to be implemented in
NumPy:
- The ``__numpy_implementation__`` attribute is documented and officially
supported as a way to defer to NumPy's own implementation.
- I have noted that dispatcher functions should be given the same name as
implementations, which should result in more interprettable error messages.
|
| |
|
| |
|
| |
|
|\
| |
| | |
MAINT: disable `__array_function__` dispatch unless environment variable set
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Per discussion on the mailing list, __array_function__ isn't quite ready to
release as part of NumPy 1.16:
https://mail.python.org/pipermail/numpy-discussion/2018-November/078949.html
We'd like to improve performance a bit, and it will be easier to support
introspection on NumPy functions if we support Python 3 only.
So for now, you need to set the environment variable
``NUMPY_EXPERIMENTAL_ARRAY_FUNCTION=1`` to enable dispatching.
|
|/
|
|
|
| |
Per our discussion on the mailing list:
https://mail.python.org/pipermail/numpy-discussion/2018-November/078911.html
|
|\
| |
| | |
NEP: tweak and mark NEP 0027 as final
|
| | |
|
|/ |
|
| |
|
| |
|
|\
| |
| | |
NEP: add notes about updates to NEP-18
|
| | |
|
| |
| |
| |
| | |
As discussion in GH12140
|
|\ \
| | |
| | | |
NEP: Add zero-rank arrays historical info NEP
|
| | | |
|
| | | |
|
| |/ |
|
|\ \
| | |
| | | |
Mark NEP 22 as accepted, and add "Informational" NEPs to NEP 1
|
| | |
| | |
| | |
| | | |
The text is lightly adapted from PEP 1.
|
| |/ |
|
| | |
|
| | |
|
| | |
|
|/ |
|
|
|
|
|
|
|
| |
The main change is replacing `try_array_function_override` with
`array_function_implementation_or_override` (our current implementation).
I also fixed a few typos.
|
|\
| |
| | |
NEP: backwards compatibility and deprecation policy
|
| |
| |
| |
| | |
[ci skip]
|
| |
| |
| |
| | |
Also fix some typos.
|
| | |
|
| | |
|
| |
| |
| |
| | |
[ci skip]
|
| |
| |
| |
| | |
Rescued from a non-linked file under numpy.org
|
| |
| |
| |
| | |
Rescued from ancient history.
|
| | |
|