Consider making warnings PEP 565 compliant
See original GitHub issuePEP 565, accepted in 3.7, redefined the semantics of several types of warnings. In particular:
For library and framework authors that want to ensure their API compatibility warnings are more reliably seen by their users, the recommendation is to use a custom warning class that derives from
DeprecationWarning
in Python 3.7+, and fromFutureWarning
in earlier versions.
Which means that AstropyDeprecationWarning
is maybe not as visible as we think, and perhaps it should derive from FutureWarning
in Python < 3.7.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:5 (5 by maintainers)
Top Results From Across the Web
PEP 565 – Show DeprecationWarning in __main
To improve this situation, this PEP proposes a single adjustment to the default warnings filter: displaying deprecation warnings attributed to the main ...
Read more >add compile option to hide binary size warnings · Issue #2221
Hi, I propose to add an option (by default not enabled) to hide the binary size warnings that are in general useful but...
Read more >Prohibited Transaction Exemption 2020-02, Improving ...
This document contains a class exemption from certain prohibited transaction restrictions of the Employee Retirement Income Security Act of ...
Read more >How to globally disable PEP 495 warnings? - python
Add this comment at the end of the line # noqa. NOQA stands for No Quality Assurance. It tells the interpreter/compiler/code analysis ...
Read more >OFAC Consolidated Frequently Asked Questions
Please review the Office of Compliance and Enforcement (“OCE”) Data Delivery ... OFAC does not need to examine samples of the actual product...
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 FreeTop 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
Top GitHub Comments
My vote would be to let python catch up with us…
and it wouldn’t be the first time :trollface: