➜

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 ncoghlan
Recipients Aaron.Meurer, Jim.Jewett, The Compiler, ezio.melotti, jayvdb, martin.panter, mbussonn, ncoghlan, njs, r.david.murray, rbcollins, serhiy.storchaka, takluyver, terry.reedy, vstinner
Date 2017-11-14.01:04:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1510621442.48.0.213398074469.issue24294@psf.upfronthosting.co.za>
In-reply-to
Content 
I don't think anybody consistently does proper resource management in the REPL, so the trade-offs involved there are quite different from those for deprecation warnings.

Assuming PEP 565 gets accepted, we'll end up with once-per-session warnings for use of deprecated APIs (due to the REPL's perpetually reset line counter, as per issue 1539925), and that seems like a good level of notification to me (not too noisy, not so unobtrusive as to never be seen at all)
History
Date User Action Args
2017-11-14 01:04:02ncoghlansetrecipients: + ncoghlan, terry.reedy, vstinner, rbcollins, ezio.melotti, r.david.murray, njs, Aaron.Meurer, takluyver, martin.panter, Jim.Jewett, serhiy.storchaka, The Compiler, jayvdb, mbussonn
2017-11-14 01:04:02ncoghlansetmessageid: <1510621442.48.0.213398074469.issue24294@psf.upfronthosting.co.za>
2017-11-14 01:04:02ncoghlanlinkissue24294 messages
2017-11-14 01:04:01ncoghlancreate