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 njs
Recipients Eric Wieser, abarry, asmeurer, mark.dickinson, ncoghlan, njs, r.david.murray, rhettinger, serhiy.storchaka, terry.reedy
Date 2019-08-05.05:29:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I think we haven't *actually* done a proper DeprecationWarning period for this. We tried, but because of the issue with byte-compiling, the warnings were unconditionally suppressed for most users -- even the users who are diligent enough to enable warnings and look at warnings in their test suites.

I can see a good argument for making the change, but if we're going to do it then it's obviously the kind of change that requires a proper deprecation period, and that hasn't happened.

Maybe .pyc files need to be extended to store a list of syntax-related DeprecationWarnings and SyntaxWarnings, that are re-issued every time the .pyc is loaded? Then we'd at least have the technical capability to deprecate this properly.
Date User Action Args
2019-08-05 05:29:05njssetrecipients: + njs, rhettinger, terry.reedy, mark.dickinson, ncoghlan, r.david.murray, serhiy.storchaka, abarry, asmeurer, Eric Wieser
2019-08-05 05:29:05njssetmessageid: <>
2019-08-05 05:29:05njslinkissue32912 messages
2019-08-05 05:29:05njscreate