Skip to content
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

Deprecate catch_warnings and raises in favor of pytest machinery? #6761

Closed
pllim opened this issue Oct 17, 2017 · 2 comments · Fixed by #12633
Closed

Deprecate catch_warnings and raises in favor of pytest machinery? #6761

pllim opened this issue Oct 17, 2017 · 2 comments · Fixed by #12633

Comments

@pllim
Copy link
Member

pllim commented Oct 17, 2017

For example, some catch_warnings can be replaced with pytest.warns (see https://docs.pytest.org/en/latest/warnings.html#warns). As a result, do we still need warning related functionality in astropy/tests/helper.py?

@mhvk
Copy link
Contributor

mhvk commented Oct 21, 2017

I've wondered too whether pytest has caught up with our custom machinery; it would certainly be nice to be as compliant as possible in our tests.

@pllim
Copy link
Member Author

pllim commented Jun 17, 2020

Started an attempt at #10504 .

UPDATE: With that PR merged, we no longer use catch_warnings or raises from helper.py but it doesn't stop them from creeping back in until we start to deprecate them. Deprecation is a battle for another day.

@pllim pllim self-assigned this Jun 17, 2020
@pllim pllim changed the title Replace warning handlers with pytest machinery? Deprecate catch_warnings and raises in favor of pytest machinery? Jul 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants