enable_deprecations_as_exceptions doesn't raise AstropyDeprecationWarnings
See original GitHub issueastropy issues a few AstropyDeprecationWarnings but these are not caught in affiliates due to some bugs, even when using enable_deprecations_as_exceptions as discussed here: https://github.com/astropy/ccdproc/pull/507#issuecomment-306910781
Issue Analytics
- State:
- Created 6 years ago
- Comments:14 (14 by maintainers)
Top Results From Across the Web
Python warnings system — Astropy v5.2
Astropy uses the Python warnings module to issue warning messages. ... which can be used to disable deprecation warnings from Astropy only.
Read more >Test failure in test_update_resized_header in io.fits on Windows ...
We only turn deprecation warnings (but not AstropyDeprecationWarning ) into exceptions. Other warnings will not be turned into exception. Is this the only...
Read more >How to ignore deprecation warnings in Python - Stack Overflow
You should just fix your code but just in case, import warnings warnings.filterwarnings("ignore", category=DeprecationWarning).
Read more >astropy.utils.decorators — gammapy v0.7
The deprecation warning will tell the user about this alternative if provided. pending : bool, optional If True, uses a AstropyPendingDeprecationWarning ...
Read more >Release Notes — NumPy v1.16 Manual
Positive will now raise a deprecation warning for non-numerical arrays¶ ... The sole exception are functions for explicitly casting to NumPy ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Maybe this has to do with when the deprecation is issued. For
gzipthis was during test-collection phase whileoverwritehappened inside a test.Indeed. Also this will be a bugfix, so no rush to get into 2.0, 2.0.1 will be just as good.