| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Fixes #8588
|
|\
| |
| | |
MAINT: Remove __setslice__ and __getslice__
|
| |
| |
| | |
Replaces getslice and setslice which have been removed.
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
This code was only here for Python 2.5 compatibility, but numpy requires 2.7
at minimum
|
| |
| |
| |
| |
| |
| | |
The example with `newaxis` now looks rather silly. I left it
because it is the only place in this tutorial with an example
how to use `newaxis`.
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* ENH: hard-code finfo parameters for known types
Hard-code the MachAr parameters for float64, float32, 80-bit extended
precision, to save time, and provide skeleton for more difficult types
such as the double double on PPC; see
https://github.com/numpy/numpy/issues/2669
* ENH: add PPC long double finfo
Add parameters for PPC long double, fixing long-standing bug for finfo
on PPC.
* BF: use Python floats for float64 finfo
For some reason (garrgh) np.exp2 with float64 gives a different answer on
Windows than it does on other platforms; use Python floating point
calculations instead, which do appear to be consistent.
* DOC: add release notes for finfo fixes
Add release note describing fixes for PPC long double ``finfo``.
* RF: try using byte string to identify floats
From suggestion by Chuck, and
https//perl5.git.perl.org/perl.git/blob/3118d7d684b56cbeb702af874f4326683c45f045:/Configure
* TST: add tests for reasonable finfo parameters
Check that finfo returns somewhat reasonable parameters for all floating
point types.
* RF: add warning for not-recognized float type
Warn if we don't have a signature for the float type.
* NF: add IEEE float128 type signature
Still needs test on platform with IEEE float128, to check MachAr-like
parameters are correct.
|
|
|
| |
DOC: fix error in arrays.ndarray.rst again
|
|
|
| |
corrected formula for n_offset and d_j
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Previously `bool(dtype(...))` would fallback to the default
implementation of `__nonzero__`, which checks if `len(object) > 0`.
Since `dtype` objects implement `__len__` as the number of record
fields, `bool` of scalar dtypes like `bool(dtype('i8'))` would evaluate
as `False`. This fixes that by implementing `__nonzero__` to always
return True.
Fixes #6294.
|
|
|
| |
MAINT: Fix building extensions with MinGW in WinPython 3.4
|
|\
| |
| | |
ENH: Vectorize packbits with SSE2
|
| | |
|
| |
| |
| |
| | |
[ci skip]
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
The following files were updated during the NumPy 1.12.0 release
- .mailmap
- doc/release/1.12.0-notes.rst
- tools/announce.py
- pavement.py
and are forward ported to master by this PR.
[ci skip]
|
|\
| |
| | |
BUG: fix set memmap offset attribute correctly when offset is greater than mmap.ALLOCATIONGRANULARITY
|
| |
| |
| |
| | |
when offset is greater than mmap.ALLOCATIONGRANULARITY
|
|/
|
|
| |
numpy https://github.com/numpy/numpy/pull/306/files is from 2012.
|
|
|
|
|
|
| |
The bug that +/- inf where not treated correctly in
np.testing.assert_array_less changed the behavior and is thus mentioned
in the release notes.
|
| |
|
|
|
|
| |
[ci skip]
|
|
|
|
| |
[ci skip]
|
|
|
|
| |
[ci skip]
|
|\
| |
| | |
Fix building extensions with MinGW for Python 3.5
|
| |
| |
| |
| |
| |
| |
| | |
MinGW can be used to build extensions, but will most likely fail for
extensions that uses the runtime extensively. This is just a band-aid
until Mingwpy is fully functional for calculation code written in
Fortran.
|
|/ |
|
|
|
|
|
|
| |
This affects mostly old boolean indexing behavior that was deprecated in
NumPy 1.9. At the time the new behavior was causing errors in a number
of downstream projects, hopefully that has been taken care of.
|
|\
| |
| | |
DEP: Handle expired deprecations.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This only applies to object arrays. Previously object identity would
override object comparison failures, comparison of objects that did not
return a boolean (arrays), and comparison of objects where the
comparison result did not agree with the object identity result (NaNs)
The first two behaviors have been deprecated since 1.9 and now return
errors. The last has issued a FutureWarning since 1.9 and now returns
the result of the comparison.
|
| |
| |
| |
| | |
Subtracting a bool_ from a bool_ was deprecated in NumPy 1.9
|
| |
| |
| |
| | |
The unary minus of booleans was deprecated in NumPy 1.9.
|
| |
| |
| |
| |
| |
| |
| | |
NpyIter_AdvancedNew raises ValueError when `oa_ndim == 0` and
`op_axes` is NULL.
Deprecated since NumPy 1.8.
|
| |
| |
| |
| | |
Non-integer index has been deprecated since NumPy 1.8.0.
|
| |
| |
| |
| |
| |
| | |
These changes have been warned of since numpy 1.7.0 for the == case and
since numpy 1.8 for the != case. This makes both operators compare
element-wise for this case.
|
|/
|
|
| |
Fixes #2865.
|
|
|
|
|
|
| |
This behaviour matches that for most other numpy functions (such as
np.mean). It was initially slated for 1.12, but replaced by a
FutureWarning. Hence, this is for 1.13.
|
|
|
|
|
|
|
| |
Change markup of title so that it works properly on the Github releases
page.
[ci skip]
|
|
|
|
| |
[ci skip]
|
| |
|
| |
|
|\
| |
| | |
MAINT: Prepare for 1.13.0 after 1.12.x branch
|
| |
| |
| |
| | |
[ci skip]
|
|/
|
|
|
|
|
| |
Fix spelling, arrangement, markup, etc. This is more a first pass
than a finishing touchup.
[ci skip]
|
|\
| |
| | |
ENH: Refactor numpy ** operators for numpy scalar integer powers
|
| |
| |
| |
| | |
[ci skip]
|
|\ \
| | |
| | | |
ENH: Add a float_power function with at least float64 precision.
|
| | |
| | |
| | |
| | | |
[ci skip]
|