| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
override `__array_ufunc__`.
|
|
|
|
|
| |
* NEP 0051 is recent
* NEP 0021 is older, I don't know why the typo hadn't been previously caught
|
|
|
| |
Co-authored-by: Inessa Pawson <inessapawson@gmail.com>
|
| |
|
| |
|
| |
|
|\
| |
| | |
DOC: Add releases to NEP 29
|
| | |
|
|/ |
|
|\
| |
| | |
BUG: -unsigned_int(0) no overflow warning
|
| |
| |
| | |
Co-authored-by: Matti Picus <matti.picus@gmail.com>
|
| |
| |
| |
| | |
All other operators should have been fixed now, many recently.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* NEP: Initial draft for a NEP to change NumPy scalar representation
* NEP: Propose to use ``np.`` prefix consistently.
* NEP: Clarify that the PR actually already went beyond booleans
* Add additional notes on longlong and Decimal(repr(scalar))
* NEP: Introduce ``get_formatter()`` and mention changes to void/MA
Also mention the backwards-incompatible break of changing ``arr.tofile()``
* Small updates, mainly because I now also use ``str`` and not just ``repr``
* DOC: Add note about non-finite values
The current choice is `np.float64(nan)` and not one of the alterntives...
* DOC: minor wording/formatting fixups.
* NEP: Address Ross' reviews of NEP 51
Co-authored-by: Sebastian Berg <sebastianb@nvidia.com>
Co-authored-by: Ross Barnowski <rossbar@berkeley.edu>
|
|/ |
|
| |
|
|\
| |
| | |
MAINT: Fix typos found by codespell
|
| | |
|
|/ |
|
| |
|
| |
|
| |
|
|
|
| |
Co-authored-by: Stefan van der Walt <sjvdwalt@gmail.com>
|
|
|
|
| |
Credit to @stefanv for wording.
|
|\
| |
| | |
DOC: update NEP29 to address PEP0602
|
| |
| |
| | |
Co-authored-by: Matti Picus <matti.picus@gmail.com>
|
| | |
|
|\ \
| | |
| | | |
DOC: Add missing links for NEP36 and NEP49
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | | |
Co-authored-by: Stefan van der Walt <sjvdwalt@gmail.com>
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
As per comment by Ross. float64 can be put at the same precision
as "uint64". This is incorrect, but it is the practical choice
that NumPy uses.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
But I need to link to the old behaviour explenatation early on
somewhere...
And possibly it is now too much. Plus, I am not sure the table
is actually all *that* useful
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Even if I prefer not to mention the word "category" too much, integral vs. inexact
is the "magic" boundary when it comes to Python promoting an numpy
scalar to the higher category.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
This may be a bit "too much" information, but on the other hand it
is a backcompat break
|
| | | |
|
| | |
| | |
| | |
| | | |
Based on Tylers and Jake Vanderplas' comments.
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Note, this really is a very early draft. For myself, I have not
even 100% made up my mind that this is actually the best approach.
However, to solicitate feedback and input, I would like to put it
out there (and have a nice rendered version).
For those mainly interested in the possible different approaches
(i.e. making decisions), the "Alternatives" section is probably most
interesting.
Please make a note of blatend errors or unnecessary repitition, but
don't be too surprised if you see them, I will not be surprised if
this needs to be redone from scratch eventually.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Changed files are
- doc/HOWTO_RELEASE.rst
- doc/Makefile
- doc/changelog/1.15.0-changelog.rst
- doc/changelog/1.16.0-changelog.rst
- doc/changelog/1.17.0-changelog.rst
- doc/changelog/1.19.0-changelog.rst
- doc/changelog/1.21.0-changelog.rst
- doc/neps/nep-0045-c_style_guide.rst
- doc/source/dev/howto_build_docs.rst
- doc/source/dev/releasing.rst
- doc/source/reference/distutils_guide.rst
- doc/source/reference/testing.rst
- doc/source/release/1.7.0-notes.rst
- doc/source/release/1.8.0-notes.rst
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* DOC: contigous -> contiguous
* DOC: enlongated -> elongated
* DOC: thuse -> thus
* DOC: quantityt -> quantity
* DOC: suppled -> supplied
* DOC: intgrally -> integrally
* DOC: assignnent -> assignment
* DOC: homoegeneous -> homogeneous
* DOC: interpereted -> interpreted
* DOC: optimised -> optimized
* DOC: Advantanges -> Advantages
* DOC: realised -> realized
* DOC: parametrizing -> parameterizing
* DOC: realised -> realized
* DOC: intrisics -> intrinsics
* DOC: ablility -> ability
* DOC: intrisic -> intrinsic
* DOC: unversal -> universal
* DOC: machnisms -> mechanisms
* DOC: specfiy -> specify
* DOC: exclution -> exclusion
* DOC: optimzations -> optimizations
* DOC: declrations -> declarations
* DOC: auto-gernreated -> auto-generated
* DOC: it highely recomaned -> it is highly recommended
* DOC: exectuing -> executing
* DOC: strectched -> stretched
* DOC: foriegn -> foreign
* DOC: indeded -> intended
* DOC: multimdimensional -> multidimensional
* DOC: supserseded -> superseded
* DOC: generalisation -> generalization
* FIX: whitespace before comma
|