| Commit message (Collapse) | Author | Age | Files | Lines |
| |\
| |
| | |
DOC: revert PR #13058 and fixup Makefile
|
| | | |
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* BUG: Use subprocess.check_output to avoid leaking file handles
This emitted a ResourceWarning as previously written, as the streams never got closed.
This change also detects errors in `svnversion` and `hg`, rather than ignoring the error code and hoping stdout contains a revision anyway.
* BUG: Fix distutils.get_version on python 3
Previously, this would throw `TypeError: cannot use a string pattern on a bytes-like object`, which would then be silenced and never seen.
The previous commit stopped silencing this error, so now everything is visibly broken rather than silently broken
Changing the strings to raw strings fixes the problem
* BUG: Don't use `close_fds`, which fails on windows
This argument was introduced along with subprocess in f5afa7836d56640f25ff3fbd2c59b8dcf016e26f to replace `popen4`, and probably wasn't necessary in the first place.
|
| |\
| |
| | |
DOC: update docstring in numpy.interp docstring
|
| | |
| |
| |
| | |
Adding 'strictly' to make the conditions to be met by the `xp` argument even more clear.
Following the suggestion in https://github.com/numpy/numpy/issues/10448#issuecomment-468302058 .
|
| | | |
|
| | | |
|
| |/ |
|
| |\
| |
| | |
DOC: Draw more attention to which functions in random are convenience wrappers
|
| | |
| |
| |
| | |
In response to twitter conversations that complain that `randn` is inconsistent with `zeros`, to which the answer is "that's because randn is a wrapper to make things look like matlab".
|
| | |
| |
| |
| | |
This gives an error at least as far back as 1.12.x
|
| |\ \
| | |
| | | |
MAINT: Convert property to @property
|
| | | | |
|
| | | | |
|
| | | | |
|
| | |/ |
|
| |\ \
| | |
| | | |
DOC: Added maximum_sctype to documentation
|
| | | | |
|
| |\ \ \
| | | |
| | | | |
BUG: remove error-prone borrowed reference handling
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | | |
BLD: Windows absolute path DLL loading
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
* Test for DLL pollution in numpy/.libs/ in Azure
CI Windows Python 3.6 builds
* emit a warning with DLL names when > 1 are present
in numpy/.libs/
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
* add an Azure CI test to mimic recent
Anaconda DLL path resolution restrictions
that prevent NumPy imports
* patch numpy.core initialization to use
absolute DLL path loading to overcome
the scenario described above
|
| |\ \ \ \ \
| |_|_|/ /
|/| | | | |
MAINT: Extract the loop macros into their own header
|
| | | | | |
| | | | |
| | | | |
| | | | | |
@{ is doxygen syntax, which we're not actually using - but it at least makes it sort of possible to see the scope of the comment.
|
| | | |_|/
| |/| |
| | | |
| | | | |
This makes it possible to use them in other source files (if we go down a source-per-ufunc approach later), and if nothing else makes a very long file a little less long.
|
| |\ \ \ \
| | | | |
| | | | | |
ENH: Adding a count parameter to np.unpackbits
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Tests are included.
Couple of minor fixes:
- Fixed packbits/unpackbits docs to reflect proper keyword names
- Added .pytest_cache to .gitignore
|
| |\ \ \ \ \
| |/ / / /
|/| | | | |
ENH: Correct handling of infinities in np.interp (option B)
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Alternative to gh-12978, using a method that does not need a lot of special cases.
This is likely more robust in the face of overflow
Fixes gh-12951.
|
| |\ \ \ \ \
| |_|_|_|/
|/| | | | |
BUG: parse shell escaping in extra_compile_args and extra_link_args
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Thanks to a change in exec_command, these strings are no longer passed onto the shell.
Since config files do not support list values, our best bet is to perform shell-splitting immediately.
This brings the behavior back in line a little to how it was before.
On windows systems, the behavior has changed. Previously it was treated as a single argument unless it contained quotes, resulting in the following weird behavior:
# passes as one argument, preserving spaces
extra_link_args=-Wl,rpath=A:/path/with spaces
# passes as two arguments, preserving spaces
extra_link_args="-Wl,rpath=A:\path\with spaces" -lgfortran
# passes as one long quoted argument (surprising and undesirable)
extra_link_args=-Wl,rpath=A:\path\without_spaces -lgfortran
Now it behaves as windows escaping via subprocess (but _not_ via cmd) normally would:
# Passed as two separate arguments (probably not as intended, but should be expected)
extra_link_args=-Wl,rpath=A:/path/with spaces
# passes as two arguments, preserving spaces
extra_link_args="-Wl,rpath=A:\path\with spaces" -lgfortran
# passes as two arguments
extra_link_args=-Wl,rpath=A:\path\without_spaces -lgfortran
Fixes gh-12659
|
| | |_|/ /
|/| | |
| | | |
| | | | |
extensibility in ufunc generator
|
| |\ \ \ \
| | | | |
| | | | | |
BUG: Fix regression in parsing of F90 and F77 environment variables
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Fixes gh-12979
Among other things, this means setting the `F90` environment variable to `"path to/f90" --coverage` works again.
|
| |/ / / /
| | | |
| | | |
| | | |
| | | |
| | | | |
Collapsing none of the axes on an array with no axes should be expected to work just fine.
Relates to gh-12130
|
| |\ \ \ \
| |/ / /
| | | | |
BUG: Changes to string-to-shell parsing behavior broke paths with quotes
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
There are places in distutils where we accept a single string from the user, and interpret it as a set of command line arguments.
Previously, these were passed on as a string unmodified to exec_command, and interpreted by subprocess in a platform-specific way.
Recent changes to distutils now pass a list of arguments to subprocess, meaning we have to split the strings ourselves.
While `shlex.split` is perfect on posix systems, it is not a good approximation of either the old or the expected behavior on windows.
Provides the building blocks needed to fix gh-12979
|
| |\ \ \ \
| | | | |
| | | | | |
BUG: fix signed zero behavior in npy_divmod
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Previously when doing floor division numpy would sometimes return an incorrect
signed zero. For example:
>>> np.zeros(10)//1
array([-0., -0., -0., -0., -0., -0., -0., -0., -0., -0.])
>>> np.remainder(-1.0,1.0)
-0.0
The reason for this is that whenever div or mod were zero the code was using
the following to pick the sign of zero:
floordiv = (a / b > 0) ? 0.0@c@ : -0.0@c@;
This commit updates these lines to instead use the copysign function which is
how cpython does floor division.
Fixes #12841.
|
| | |_|_|/
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
(#12973)
* DOC: Recommend using reshape instead of matrix for vector transpose
* Rephrase doc advice for 1-D vector transpose
Recommend adding a dimension instead of using `reshape`.
Per @eric-wieser, makes explanation more technical.
* Fix grammar
|
| |\ \ \ \
| | | | |
| | | | | |
BUG: do not catch stderr when checking compiler version
|
| | | | | |
| | | | |
| | | | | |
which used to fail for ifort
|
| | |_|_|/
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The pickle module was being imported from numpy.core.numeric. It was
defined there in order to use pickle5 when available in Python3 and
cpickle in Python2. The numpy.compat module seems a better place for
that.
|
| |\ \ \ \
| | | | |
| | | | | |
MAINT: Use the same multiplication order in interp for cached and uncached slopes
|