Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Timeline for removal of deprecated astropy.tests.pytest_plugins
See original GitHub issueImporting from astropy.tests.pytest_plugins was officially deprecated in the 3.0 release, but has been maintained for backwards compatibility (see #6606 and specifically c16c2fa).
However, the discussion on https://github.com/astropy/pytest-doctestplus/issues/22 seems to indicate that imports of the form from astropy.tests import pytest_plugins are definitively broken with recent versions of pytest.
This raises a question: should we move forward with the removal of the astropy.tests.pytest_plugins submodule earlier than we would for other deprecations?
cc @nicoddemus
Issue Analytics
- State:
- Created 5 years ago
- Comments:21 (21 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I suppose that’s the only solution as we are not suppose to remove any API from LTS.
I suspect the only up-to-date users of LTS is the CI for the affiliated packages 😉
@pllim at that time it was not clear (or I was not paying attention) that this would be completely broken by
pytest-4.0and/or when exactly 4.0 would be released. So in light of that information, I think it should be removed as soon as possible.