| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
After the recent patch to CCompiler.spawn, the file-paths no longer need manual quoting - that's handled as needed within subprocess.
Fixes #12411
|
|
|
|
|
|
|
| |
If locale.getpreferredencoding(False) returns Null,
the build fails, since commit 5652b0785.
This seems to be not really necessary; here we
provide a fallback to 'ascii' locale if needed.
|
|\
| |
| | |
MAINT: remove exec_command usage from ccompiler.py
|
| |
| |
| |
| |
| |
| | |
* replaced the usage of exec_command() in
ccompiler distutils module with subprocess
equivalent
|
|/
|
|
| |
Closes https://github.com/scipy/scipy/issues/9452
|
|\
| |
| | |
MAINT: delay import of distutils.msvccompiler to avoid warning on non-Windows.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
*Importing* distutils.msvccompiler works on non-Windows systems, but
triggers a pointless "warning" (using distutils' own logging system;
"Can't read registry etc.") Delay the import so that other uses of
distutils.misc_util are not affected.
When running distutils commands, the verbosity is set by default to 1
(`self.verbose = 1` in distutils/dist.py) so the warning does get
displayed.
To trigger the warning, subclass e.g. build_ext, override its
finalize_options method, import numpy.distutils.misc_util from there,
and then pass the new build_ext as cmdclass to setuptools.setup().
Partially reverts 15f52f5.
|
| | |
|
| |
| |
| |
| |
| |
| | |
The default value for get_num_build_jobs() is now the number of CPUs
limited to a maximum of 8. This is to prevent overloading systems
with a lot of CPUs. See ticket #12087
|
|\ \
| | |
| | | |
MAINT: remove redundant imports
|
| | | |
|
|\ \ \
| | | |
| | | | |
MAINT: remove unused stdlib imports
|
| |/ / |
|
|/ / |
|
| | |
|
|\ \
| | |
| | | |
MAINT: remove usage of exec_command in config.py
|
| | |
| | |
| | |
| | |
| | |
| | | |
* replace usage of exec_command() with standard
library equivalent in the distutils config
module
|
|/ /
| |
| |
| | |
Replaced the usage of exec_command() in distutils ibm module with subprocess.check_output
|
|\ \
| | |
| | | |
MAINT: flake8 cleanups
|
| |/ |
|
| |
| |
| |
| |
| |
| |
| | |
* the single usage of exec_command in
distutils build_ext module has been
replaced with a standard library usage
of subprocess
|
| |
| |
| |
| |
| |
| | |
* replace exec_command() with its standard
library equivalent in distutils system_info
module
|
|/
|
|
|
|
| |
* replaced usage of exec_command() with
standard library equivalent in distutils
gnu module
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
unnecessary import dependencies
pytesttester is used by every single subpackage, so making it depend on np.testing just creates cyclic dependencies that can lead to circular imports
Relates to #11457
|
|
|
|
|
|
|
|
|
|
|
| |
Numpy wheels on Windows were clearing the ctypes path when they loaded
the OpenBLAS DLL, leading to failure of DLL loads subsequent to NumPy
import because the needed DLLs could not be found.
This isn't a straight revert, it restores to the 1.15.x version of
the relevant code.
Closes #11431.
|
| |
|
|\
| |
| | |
BLD: cleanup _configtest.o.d during build
|
| | |
|
|/
|
|
|
|
|
|
|
|
| |
so that the python-scikit-learn openSUSE package
that uses config.add_extension(name, "path/to/*.cpp", ...)
builds in a reproducible way
in spite of indeterministic filesystem readdir order
and http://bugs.python.org/issue30461
See https://reproducible-builds.org/ for why this is good.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove the special-cased handling of OSX Accelerate/vecLib libraries,
and move the code (which was duplicated in two places) to a new
accelerate_info class, which is used in the same way as openblas/etc
libs.
Also add a configuration section and an environment variable for
controlling whether Accelerate/vecLib is to be used or not. Previously,
it was not possible to use generic BLAS/LAPACK instead of Accelerate on
OSX.
|
|\
| |
| | |
Add missing underscore to prototype in check_embedded_lapack
|
| | |
|
| | |
|
|/ |
|
|
|
|
|
| |
That function is nose specific and has not worked since `__init__` files
were added to the tests directories.
|
|
|
|
|
|
|
|
| |
Numpy can now be tested using the standard
`python -c"import numpy; numpy.test()"`
construct.
|
|
|
|
|
|
|
|
|
|
|
| |
Use standard pytest markers everywhere in the numpy tests. At this point
there should be no nose dependency. However, nose is required to test
the legacy decorators if so desired.
At this point, numpy test cannot be run in the way with runtests, rather
installed numpy can be tested with `pytest --pyargs numpy` as long as
that is not run from the repo. Run it from the tools directory or some
such.
|
|
|
|
|
|
|
|
|
| |
This is to prepare for the switch to pytest.
* Rename `numpy/testing/nose_tools` to `numpy/testing/_private`.
* Redirect imports as needed.
* Copy `_testutils.py` from scipy to `numpy/testing/_private`.
* Rename `_testutils.py` to `_pytester.py` and remove unneeded bits.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This removes a few left over uses of unittest. The main changes apart
from removal of Test case are:
* `setUp` replaced by nose and pytest compatible `setup`
* `tearDown` replaced by nose and pytest compatible `teardown`
* `assertRaises` replaced by `assert_raises`
* `assertEqual` replaced by `assert_equal`
The last two are in `numpy/testings/tests/test_utils.py`, so may seem a
but circular, but at least are limited to those two functions.
The use of `setup` and `teardown`, can be fixed up with the pytest
equivalents after we have switched to pytest.
|
| |
|