question-mark
Stuck on an issue?

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.

Consider making warnings PEP 565 compliant

See original GitHub issue

PEP 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 from FutureWarning 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:closed
  • Created 5 years ago
  • Reactions:1
  • Comments:5 (5 by maintainers)

github_iconTop GitHub Comments

3reactions
mhvkcommented, Feb 28, 2019

My vote would be to let python catch up with us…

1reaction
bsipoczcommented, Feb 28, 2019

My vote would be to let python catch up with us…

and it wouldn’t be the first time :trollface:

Read more comments on GitHub >

github_iconTop 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 >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found