This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gregory.p.smith
Recipients gregory.p.smith, ncoghlan, vstinner
Date 2020-03-08.00:53:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Recurring theme: The stdlib has the issue of DeprecationWarning being added to APIs we are changing or removing a few versions in the future yet we perceive that many people never actually bother to try checking their code for deprecation warnings.  Only raising issues with a documented, warned, planned in advance API change when it actually happens.

Could we reduce the chances of this by enabling DeprecationWarnings by default for processes started via unittest.main() and other common unittest entrypoints?  (other test frameworks like pytest should also consider this if they don't already; do we have any existing external implementations of this for inspiration?)

One issue with this is that some important warnings are at _parse_ time or _import_ time.  But we can deal with import time ones if we are able to have the unittest entrypoint re-exec the process with the same args but with warnings enabled.  (and _could_ surface parse time ones if we're willing to accept slower process startup by disabling use of pycs; i wouldn't go that far)

Related work:

has this idea already been discussed?  I don't remember and haven't searched backwards...
Date User Action Args
2020-03-08 00:53:52gregory.p.smithsetrecipients: + gregory.p.smith, ncoghlan, vstinner
2020-03-08 00:53:52gregory.p.smithsetmessageid: <>
2020-03-08 00:53:52gregory.p.smithlinkissue39892 messages
2020-03-08 00:53:52gregory.p.smithcreate