| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| | |
MAINT: Fix some typos in a code string and comments
|
|/ |
|
|\
| |
| | |
Fix setuptools sdist
|
| |
| |
| |
| |
| |
| | |
Warn in numpy/distutils/command/egg_info.py if using setuptools.sdist.
See gh-7127 for details.
|
| |
| |
| |
| |
| | |
This was seriously broken. Setuptools does unwanted 'smart' things and
ignores MANIFEST.in. Closes gh-7127.
|
|/ |
|
|\
| |
| | |
TST: Fixed f2py test for non-versioned python executables
|
|/
|
|
|
|
|
|
|
|
|
| |
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.
|
|\
| |
| | |
TST: Fixed f2py test for win32 virtualenv
|
|/
|
|
|
|
|
|
| |
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.
|
|\
| |
| | |
MAINT: Fix typos in docs
|
|/ |
|
|\
| |
| | |
BUG: One Element Array Inputs Return Scalars in np.random
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
|\ \
| |/
|/| |
DOC: update Python versions requirements in the install docs
|
|/ |
|
|\
| |
| | |
TST, DOC: Added Broadcasting Tests in test_random.py
|
| |
| |
| |
| |
| |
| |
| | |
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.
|
|\ \
| |/
|/| |
DOC: Update the 1.11.0 release notes.
|
| |
| |
| |
| | |
[ci skip]
|
|\ \
| | |
| | | |
BUG: Have `norm` cast non-floating point arrays to 64-bit float arrays
|
| | |
| | |
| | |
| | | |
computations are done with floating point numbers.
|
| | | |
|
| | | |
|
|/ /
| |
| |
| | |
Otherwise, weird integer roundoff errors give faulty results in some cases.
|
|\ \
| | |
| | | |
BLD: fix compilation on non glibc-Linuxes
|
| | |
| | |
| | |
| | |
| | | |
Non-glibc Linuxes dont have the __GLIBC_PREREQ function and compilation of numpy
fails on such platforms.
|
|\ \ \
| | | |
| | | | |
Revert "BLD: fix compilation on non glibc-Linuxes"
|
|/ / / |
|
|\ \ \
| |/ /
|/| | |
BLD: fix compilation on non glibc-Linuxes
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Non-glibc Linuxes dont have the __GLIBC_PREREQ function and compilation of numpy
fails on such platforms. To avoid this the TRIG_OK check should be done only in
the glibc environment
The patch is taken from AlpineLinux repository
http://git.alpinelinux.org/cgit/aports/tree/testing/py-numpy/numpy-1.10.0-musl.patch?id=2e5c4bfcf1c9746edd58a8e684d01403f234e71d
|
|\ \ \
| |/ /
|/| | |
MAINT: Update the git .mailmap file.
|
| |/
| |
| |
| | |
[ci skip]
|
|\ \
| |/
|/| |
MAINT: Simplify mtrand.pyx helpers
|
|/
|
|
|
|
|
| |
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.
|
|\
| |
| | |
REL: Update master branch after 1.12.x branch has been made.
|
|/
|
|
|
|
|
| |
* Drop testing of Python 2.6, 3.2, and 3.3
* Create 1.12.0-notes.rst and add to source/documentation.
* Update pavement.py to use 1.10.x as LOG_START
* Update version numpy in setup.py
|
|\
| |
| | |
REL: Prepare for 1.10.x branch.
|
|/
|
|
|
|
|
| |
* 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 of added functionality of the deg parameter of
the polynomial fitting functions in the numpy.polynomial package and put
it in the 'New Features' section.
|
| |/
| |
| |
| |
| |
| |
| | |
* 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
|
|\ \
| |/
|/| |
DEP: Emit FutureWarning for NAT comparisons.
|
| |
| |
| |
| |
| | |
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.
|