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 pitrou
Recipients alex, barry, eric.araujo, gvanrossum, ncoghlan, pitrou
Date 2017-11-08.09:38:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1510133923.7.0.213398074469.issue31975@psf.upfronthosting.co.za>
In-reply-to
Content
> Thus the following will start emitting DeprecationWarning by default again (as they did in 2.6 and earlier):
> - experiments at the REPL

This is backwards.  If there's one place where you *don't* want stderr polluted with warnings (or any kind of logging), it's an interactive prompt.

More generally, I think this entire proposal is unsound, and needs a PEP written to make its case clearly.
History
Date User Action Args
2017-11-08 09:38:43pitrousetrecipients: + pitrou, gvanrossum, barry, ncoghlan, eric.araujo, alex
2017-11-08 09:38:43pitrousetmessageid: <1510133923.7.0.213398074469.issue31975@psf.upfronthosting.co.za>
2017-11-08 09:38:43pitroulinkissue31975 messages
2017-11-08 09:38:43pitroucreate