Skip to content

DEP: remove deprecated (and private) numpy.testing submodules. #14567

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Sep 21, 2019

Conversation

rgommers
Copy link
Member

Removes these files that were deprecated since 1.15.0:

  • numpy/testing/decorators.py
  • numpy/testing/noseclasses.py
  • numpy/testing/nosetester.py

This also resolves a failure in the recently introduced tests in test_public_api.py (see gh-14454). Closes gh-14566

@rgommers rgommers changed the title DEP: remove deprecate (and private) numpy.testing submodules. DEP: remove deprecated (and private) numpy.testing submodules. Sep 21, 2019
Removes these files that were deprecated since 1.15.0:

- numpy/testing/decorators.py
- numpy/testing/noseclasses.py
- numpy/testing/nosetester.py

This also resolves a failure in the recently introduced tests
in `test_public_api.py` (see numpygh-14454).  Closes numpygh-14566
@charris
Copy link
Member

charris commented Sep 21, 2019

There are still folks using the NumPy nose framework so it may be a bit early to delete the files. Most of the linux distributions have patched versions of nose, so that still works. If we do remove the files there needs to be a release note.

@rgommers
Copy link
Member Author

Nothing is gone, the correct imports are and have always been

from numpy.testing import Tester, run_module_suite, dec

These files were always private, they just missed an underscore.

@mattip
Copy link
Member

mattip commented Sep 21, 2019

There are still folks using the NumPy nose framework

@charris can we ping those projects to encourage them to deprecate the old imports?

@charris
Copy link
Member

charris commented Sep 21, 2019

OK, looks like there are workarounds for any that need it. I'll do a wheels build after this is merged to check.

Thanks Ralf.

@charris charris merged commit 7594455 into numpy:master Sep 21, 2019
@charris
Copy link
Member

charris commented Sep 21, 2019

OK, the travis builds are working, but the appveyor builds are failing. I don't know if that is related.

Note that a new version of setuptools was released a month ago. I suspect that maybe things were fixed to run that check, as the numpy version cannot be available before the build takes place.

@rgommers rgommers deleted the fix-publicapi-test branch September 21, 2019 18:35
@rgommers
Copy link
Member Author

That Appveyor failure does not look related. It does look very odd though.

  File "C:\Python37-x64\lib\site-packages\setuptools\msvc.py", line 199, in msvc14_gen_lib_options
    if LegacyVersion(np.__version__) < LegacyVersion('1.11.2'):

Indeed, that can't be right, looks like a regression introduced in setuptools.

@rgommers
Copy link
Member Author

Or it got triggered by @mattip's build_src changes

@charris
Copy link
Member

charris commented Sep 21, 2019

I'm suspecting the latter, the code in setuptools is three years old.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

#14454 broke the wheel builds.
3 participants