| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
See https://docs.python.org/2/library/unittest.html#deprecated-aliases
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- Always enable __array_function__ overrides.
- Remove special cases for Python 2 compatibility.
- Document these changes in 1.17.0-notes.rst.
It will be good to see ASV numbers to understand the performance implications
of these changes. If need be, we can speed up NumPy functions internally by
using non-dispatched functions (with ``.__wrapped__``).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Example behavior:
>>> x = np.array([1, 2, 3])
>>> y = np.array([1, 2, 3.0001])
>>> np.testing.assert_allclose(x, y)
AssertionError:
Not equal to tolerance rtol=1e-07, atol=0
Mismatch: 33.3%
Max absolute difference: 0.0001
Max relative difference: 3.33322223e-05
x: array([1, 2, 3])
y: array([1. , 2. , 3.0001])
Motivation: when writing numerical algorithms, I frequently find myself
experimenting to pick the right value of `atol` and `rtol` for
`np.testing.assert_allclose()`. If I make the tolerance too generous, I risk
missing regressions in accuracy, so I usually try to pick the smallest values
for which tests pass. This change immediately reveals appropriate values to
use for these parameters, so I don't need to guess and check.
|
|
|
|
|
|
|
| |
Most of this was already done, but we were still raising an error for
declaration after a statement because the Windows Python 2.7 compiler
did not allow it. We can fix this now as NumPy >= 1.17 has dropped
Python 2.7 support.
|
|\
| |
| | |
MAINT: Update changelog.py for Python 3.
|
| |
| |
| |
| |
| |
| |
| |
| | |
- Don't use UTF8Writer in Python 3.
- Don't use print() for blank lines.
This is left compatible with Python 2 as someone may use it with
that version and there is no need to force the change.
|
|/ |
|
|
|
|
|
|
|
|
|
| |
* added lib.recfunctions to refguide
PUBLIC_SUBMODULES, as the doctests
were otherwise not getting executed
* fixed a failing doctest in
recfunctions after above activation
|
|
|
|
|
|
|
|
| |
* ported the refguide_check module from SciPy for usage
in NumPy docstring execution/ verification; added the
refguide_check run to Azure Mac OS CI
* adjusted NumPy docstrings such that refguide_check passes
|
| |
|
|
|
|
|
|
| |
* our CI should now report test
coverage for the new array_function
dispatch protocol
|
| |
|
| |
|
| |
|
|\
| |
| | |
TST: Start testing with "-std=c99" on travisCI.
|
| |
| |
| |
| |
| |
| |
| | |
[skip appveyor]
C99 looks to work with gcc for all the Python versions we currently
support. Testing with c99 is a step forward in testing #11888 before
it gets merged after we drop Python 2.7 support.
|
|/
|
|
|
|
|
|
|
|
|
| |
* BUG: Fix memory leak in pyfragments.swg
Make sure to Py_DECREF the Py_ArrayDesc created in the definition of
SWIG_CanCastAsInteger for long and unsigned long.
Fixes #11876
* fixup! BUG: Fix memory leak in pyfragments.swg
|
|
|
|
|
|
| |
* Drop Python 3.4 testing on travis and appveyor.
* Move the DEBUG build to 3.5.
* Document dropping 3.4 support in the release notes.
|
|
|
|
|
|
| |
The virtualenv version was pinned to 14.0.6, which seems to have started
causing test failures on Python 2.7 for some unknown reason. The lastest
version is 16.0.0 and that seems to fix the problem.
|
| |
|
|\
| |
| | |
BUG: Increase required cython version on python 3.7
|
| |
| |
| |
| | |
Relates to #11483
|
|/ |
|
|
|
|
| |
Before, we did the worst of both worlds, checking the version of one then calling the other.
|
|
|
|
| |
Run it using python -m cython, which works fine even on 0.19
|
| |
|
| |
|
| |
|
|
|
|
|
| |
For the time being, these tests will ignore the flood of deprecated
yield test warnings. Fixing those is for another PR.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Upload devdocs and neps after build
* Install numpydoc
* Fix masked array documentation injection
`doc_note` appends a `Notes` section to docstrings, which may lead to
duplicate sections.
* Add deploy key for neps repo
Note that we have to explicitly reset the ~/.ssh/config to only leave
one SSH key
* Only deploy on master branch
* Blow away previous dev docs after each upload
* Add tool to upload files to remote repo
* Remove numpydoc from pip install; it is included as a submodule
* Avoid using invalid escape code
* Rename repo upload tool
* Use check_call to simplify doc pushing tool
|
|
|
|
|
|
|
|
|
|
| |
* MAINT: Replace print statements for Python3.
Updates tools/swig/test/testSuperTensor.py.
* MAINT: Fix deprecated escaped characters for python 3.6+.
Update numpy/linalg/lapack_lite/clapack_scrub.py.
|
| |
|
|
|
|
| |
Leave the flag if there's only one non unit dim
|
|
|
|
|
|
|
| |
Otherwise the returned array has both flags, which creates all sorts of confusing runtime behaviors.
C_CONTIGUOUS : True
F_CONTIGUOUS : True
Doesn't cause a crash, but some functions like copy() works in F_CONTIGUOUS others like element wise operators assume C_CONTIGUOUS, obviously this becomes a nightmare to debug.
|
|\
| |
| | |
MAINT: Move `tools/announce.py` to `tools/changelog.py`.
|
| |
| |
| |
| | |
[skip ci]
|
| | |
|
|/
|
|
|
|
| |
The zesty release hit end of life Jan 13, 2018 and it seems that travis
ci tests are failing due to a failure to fetch it. This updates to use
artful. When the bionic LTS comes out in April, we should update again.
|
| |
|
|
|
|
| |
See https://github.com/travis-ci/travis-ci/issues/8920 .
|
|
|
|
|
|
| |
Disable "-Wsign-compare" and "-Wunused-result" gcc warnings.
These seem to have been enabled by default recently for wheels
sdist builds.
|
| |
|