| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
Warn in numpy/distutils/command/egg_info.py if using setuptools.sdist.
See gh-7127 for details.
|
|
|
|
|
|
|
|
|
|
|
| |
The 'sys.executable' can come in various names, but
the three main ones are "python", "python{major_version}",
and "python{major_version.minor_version}". The current
version of the f2py test assumes that only the latter
two are used. Since "f2py" is generally versioned,
using the executable basename "python" will make it
impossible to find. This commit fixes that issue
by using a sure-fire way of getting the Python version.
|
|
|
|
|
|
|
|
| |
Fixed test_scripts.test_f2py test so that
it can pass correctly on win32 virtualenvs,
in which the Python executable and the
f2py.py file are both in the Scripts
directory.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes bug in np.random methods that would return scalars
when passed one-element array inputs. This is because
one-element ndarrays can be cast to integers / floats, which
is what functions like PyFloat_AsDouble do before converting
to the intended data type.
This commit changes the check used to determine whether the
inputs are purely scalar by converting all inputs to arrays
and checking if the resulting shape is an empty tuple (scalar)
or not (array).
Closes gh-4263.
|
|
|
|
|
|
|
| |
Clarified the output size depending on whether
scalar or non-scalar inputs are passed to
functions in mtrand.pyx that can broadcast
their arguments.
|
|
|
|
|
|
| |
Added a whole new suite of tests to ensure that
functions in mtrand.pyx which are broadcastable
actually broadcast their arguments properly.
|
|
|
|
| |
computations are done with floating point numbers.
|
| |
|
| |
|
|
|
|
| |
Otherwise, weird integer roundoff errors give faulty results in some cases.
|
|
|
|
|
| |
Non-glibc Linuxes dont have the __GLIBC_PREREQ function and compilation of numpy
fails on such platforms.
|
|
|
|
|
|
|
| |
Refactored methods that broadcast arguments
together by finding additional common ground
between code in the if...else branches that
involved a size parameter being passed in.
|
|
|
|
|
|
|
| |
* Add comment to cversions.txt (no change)
* Add comment to setup_common.py (no change)
* Nothing done for numpy/core/include/numpy/numpyconfig.h
* Update log start to 1.10.0 in pavement.py.
|
|\
| |
| | |
TST, MAINT: Lots of new tests for fromnumeric.py
|
| | |
|
|\ \
| | |
| | | |
Refactor functionality added to the numpy.polynomial package in #6360.
|
| |/
| |
| |
| |
| |
| |
| | |
* Rewrite the documentation for `deg`.
* Check that the passed degrees are int and raise if not.
* Do not accept `deg` arguments that do not convert as 0-D or 1-D.
* Sort passed degree terms for repeatability.
|
|\ \
| | |
| | | |
BUG: Should fix astype cast bug in numpy.fft module
|
| |/
| |
| |
| | |
Closes #6693
|
| |
| |
| |
| |
| | |
The behavior of NAT comparisons will change in Numpy 1.13. Make sure
that a FutureWarning is emitted when the results will change.
|
|/
|
|
|
|
| |
In Numpy 1.13 the plan is for NAT comparisons to behave like NaN
comparisons, e.g., False except for 'NAT != NAT', which will be
True. See the discussion at gh-7019 for details.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The argument `deg` is enhanced to allow an
array_like argument to past which specifies
which terms to include in the fit.
The returned coef array is exapnded to have
entries of 0 for all coefficients which were
not included in the fit.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The argument `deg` is enhanced to allow an
array_like argument to past which specifies
which terms to include in the fit.
The returned coef array is exapnded to have
entries of 0 for all coefficients which were
not included in the fit.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The argument `deg` is enhanced to allow an
array_like argument to past which specifies
which terms to include in the fit.
The returned coef array is exapnded to have
entries of 0 for all coefficients which were
not included in the fit.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The argument `deg` is enhanced to allow an
array_like argument to past which specifies
which terms to include in the fit.
The returned coef array is exapnded to have
entries of 0 for all coefficients which were
not included in the fit.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The argument `deg` is enhanced to allow an
array_like argument to past which specifies
which terms to include in the fit.
The returned coef array is exapnded to have
entries of 0 for all coefficients which were
not included in the fit.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The argument `deg` is enhanced to allow an
array_like argument to past which specifies
which terms to include in the fit.
The returned coef array is exapnded to have
entries of 0 for all coefficients which were
not included in the fit.
|
| |
|
|\
| |
| | |
ENH: Allow site.cfg information with libraries key
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This PR fixes the case when users create a site.cfg to fix
library locations, but does not change the library names.
Now numpy.distutils correctly checks all options related to
libraries by defaulting to the library from the class via _lib_names
Signed-off-by: Nick Papior <nickpapior@gmail.com>
|
|\ \
| | |
| | | |
MAINT: Add '0x' to API version error for clarity.
|
| | | |
|
|\ \ \
| |_|/
|/| | |
BUG: Handle multiple percentiles for all-nan slices in nanpercentile
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Fix bug where nanpercentile would crash with an all-nan slices when
given multiple percentiles. Also corrects behavior where array sizes
different from numpy.percentile would be returned with keepdims enabled.
Fix #5760
|
|\ \ \
| | | |
| | | | |
memcpy-based fast, typed shuffle.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Apparently gcc only specializes one branch (the last one) so I went for
another 33% performance increase (matching #6776) in what's likely the
most common use case.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Only for 1d-ndarrays exactly, as subtypes (e.g. masked arrays) may not
allow direct shuffle of the underlying buffer (in fact, the old
implementation destroyed the underlying values of masked arrays while
shuffling).
Also handles struct-containing-object 1d ndarrays properly.
See #6776 for an earlier, less general (but even faster: ~6x)
improvement attempt, #5514 for the original issue.
|
|\ \ \ \
| |/ / /
|/| | | |
Revert "Merge pull request #7001 from shoyer/NaT-comparison"
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This reverts commit 7141f40b58ed1e7071cde78ab7bc8ab37e9c5983,
reversing changes made to 8fa6e3bef26a6d4a2c92f2824129aa4409be2590.
The original broke some pandas tests. The current plan to get this
in is
* reversion
* issue FutureWarning in 1.11 and 1.12
* make the change in 1.13.
|
|\ \ \ \
| | | | |
| | | | | |
API: Make datetime64 timezone naive
|