| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
These dtypes do not really make sense as instances. We can (somewhat)
reasonably define np.dtype(np.int64) as the default (machine endianess)
int64. (Arguably, it is unclear that `np.array(arr_of_>f8, dtype="f")`
should return arr_of_<f8, but that would be very noisy!)
However, `np.integer` as equivalent to long, is not well defined.
Similarly, `dtype=Decimal` may be neat to spell `dtype=object` when you
intend to put Decimal objects into the array. But it is misleading,
since there is no special meaning to it at this time.
The biggest issue with it, is that `arr.astype(np.floating)` looks
like it will let float32 or float128 pass, but it will force a
float64 output! Arguably downcasting is a bug in this case.
A related issue is `np.dtype("S")` and especially "S0". The dtype "S"
does make sense for most or all places where `dtype=...` can be
passed. However, it is conceptionally different from other dtypes, since
it will not end up being attached to the array (unlike "S2" which
would be). The dtype "S" really means the type number/DType class
of String, and not a specific dtype instance.
|
|\ \
| | |
| | | |
BUG: Fixing result of np quantile edge case
|
| | | |
|
|/ /
| |
| |
| |
| |
| | |
Updated the description to consider all array elements
Updated the examples to use multiple elements array, to show that one element not close enough prevent for the whole array to be considered as real
Closes #15626
|
| | |
|
| | |
|
|\ \
| |/
|/| |
MAINT: cleanup unused imports; avoid redefinition of imports
|
| |
| |
| |
| |
| |
| |
| | |
* Cleanup unused imports (F401) of mostly standard Python modules,
or some internal but unlikely referenced modules
* Where internal imports are potentially used, mark with noqa
* Avoid redefinition of imports (F811)
|
|/ |
|
|
|
| |
More sys.version cleanup.
|
|
|
|
|
|
|
| |
The bug occurs since numpy 1.16. Before that empty descr corresponds to
`np.dtype([])`. This fixes the problem by following numpy 1.15's
behavior.
Closes gh-15396
|
|
|
|
|
|
|
|
|
| |
This PR uses simple cases of PEP 380 to rewrite:
for v in g:
yield v
into:
yield from <expr>
|
|\
| |
| | |
ENH: Make use of ExitStack in npyio.py
|
| | |
|
|/ |
|
|\
| |
| | |
MAINT: Replace basestring with str.
|
| |
| |
| |
| |
| |
| |
| | |
This replaces basestring with str except in
- tools/npy_tempita/
- numpy/compat/py3k.py
|
|\ \
| |/
|/| |
MAINT: Revise imports from urllib modules
|
| | |
|
|/ |
|
|\
| |
| | |
MAINT: Cleanup python2 references
|
| | |
|
|\ \
| | |
| | | |
MAINT: Python2 Cleanups
|
| |/ |
|
|/ |
|
|
|
|
| |
This implements NEP 34.
|
| |
|
| |
|
| |
|
|\
| |
| | |
MAINT: cleanup sys.version dependant code
|
| | |
|
|/ |
|
|
|
|
| |
Now that 2.7 is gone, there is no need to pop manually from kwarg dictionaries.
|
|
|
|
|
|
|
| |
Inheriting from object was necessary for Python 2 compatibility to use
new-style classes. In Python 3, this is unnecessary as there are no
old-style classes.
Dropping the object is more idiomatic Python.
|
|
|
|
|
| |
As numpy is Python 3 only, these import statements are now unnecessary
and don't alter runtime behavior.
|
|
|
|
|
|
|
| |
In numpy.gradient, convert integer array inputs to float64 to avoid
unwanted modular arithmetic.
Closes gh-15207.
|
|
|
|
| |
* Remove a few unused imports in several files.
|
|
|
|
| |
* Remove unused imports.
|
|
|
|
|
|
| |
* Remove conditional imports that handled Python 2.
* Remove unused imports.
* Partial PEP 8 clean up.
|
|
|
|
|
|
|
| |
* Remove the unused function _to_filehandle().
* Remove conditional imports that handled Python 2.
* Remove unused imports.
* Fix a few line lengths (PEP 8).
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This reverts commit c088383cb290ca064d456e89d79177a0e234cb8d and
uses the same kind casting rule for the additional keyword arguments
``to_end`` and ``to_begin``. This results in slightly more leniant
behaviour for integers (which can now have overflows that are
hidden), but fixes an issue with the handling of NaN.
Generally, this behaviour seems more conistent with what NumPy does
elsewhere. The Overflow issue exists similar in many other places
and should be solved by integer overflow warning machinery while
the actual cast takes place.
Closes gh-13103
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This reverts commit c088383cb290ca064d456e89d79177a0e234cb8d and
uses the same kind casting rule for the additional keyword arguments
``to_end`` and ``to_begin``. This results in slightly more leniant
behaviour for integers (which can now have overflows that are
hidden), but fixes an issue with the handling of NaN.
Generally, this behaviour seems more conistent with what NumPy does
elsewhere. The Overflow issue exists similar in many other places
and should be solved by integer overflow warning machinery while
the actual cast takes place.
Closes gh-13103
|
| | |
|
| |
| |
| |
| | |
Fix wrong multiplier for /proc/meminfo, and do style cleanups.
|
|\ \
| | |
| | | |
MAINT: Only copy input array in _replace_nan() if there are nans to replace
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Using generators instead of full-blown lists
Using set for search instead of list
Using min to get single element insteaf of sorting full list
|
|\ \ \
| | | |
| | | | |
DEP: issue deprecation warning when creating ragged array (NEP 34)
|
| | | | |
|