| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
the np testrunner
|
|
|
|
|
|
| |
There is a test that fails in the presence of simplefilter('ignore')
(test_warnings.py). catch_warnings(record=True) seems to be a way to get the
same behavior without failing the test.
|
|
|
|
|
| |
NumPy has dropped Python 3.7, so these are no longer necessary (and they
didn't completely work anyway).
|
|
|
|
|
| |
The array_api submodule needs to be skipped entirely, as it uses non-3.7
compatible syntax.
|
|
|
|
|
|
| |
The warning is issued on import, which otherwise breaks pytest collection. If
we manually import early and ignore the warning, any further imports of the
module won't issue the warning again, due to the way Python caches imports.
|
|
|
|
| |
of NumPy build
|
|
|
|
|
| |
_pytesttester.py had either on old implementation or a wrong one
Updated it with the current practice
|
|
|
|
| |
All configuration is now done in conftest.py, and detection of dev/user mode is based on the presence of pytest.ini in the repo root. See #17390.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Add new attributes to umath module
* __cpu_baseline__ a list contains the minimal set of required optimizations
that supported by the compiler and platform according to the specified
values to command argument '--cpu-baseline'.
* __cpu_dispatch__ a list contains the dispatched set of additional optimizations
that supported by the compiler and platform according to the specified
values to command argument '--cpu-dispatch'
- Print required and additional optimizations during the run of PytestTester
|
| |
|
| |
|
| |
|
| |
|
|
|
| |
These implemented the __getslice__ and __setslice__ methods in Python 2, which no longer exist in Python 3.
|
|
|
|
|
| |
sys.exc_clear() was removed in Python 3. All internal uses can be
removed.
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Pytest < 3.8 ignored warnings issued during test collection, but that
changed in pytest 3.8 and the method NumPy used to suppress the
PendingDeprecationWarning for matrices no longer worked, or rather, was
exposed as not working. The fix here is to suppress the warning in
pytest.ini and pytesttester.py , which should work as long as the tests
are the only places left where NumPy uses matrices.
An alternate fix is to delay the construction of matrices in the tests
until they are actually run, which has the virtue of test localization
but is a bit more complicated.
See https://github.com/pytest-dev/pytest/issues/3945 for discussion.
|
|
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
|