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 Eric Wieser, abarry, asmeurer, gregory.p.smith, lukasz.langa, mark.dickinson, ncoghlan, njs, r.david.murray, rhettinger, serhiy.storchaka, terry.reedy
Date 2019-08-06.08:08:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Can the pyc compilation step done by our normal package installers be made to treat this warning as an error so that it is forced into the package owners faces instead of overlooked because it was just something on stderr?

This syntax warning is absolutely the right thing to surface for _owners/maintainers_ of a given piece of code.  Their strings are wrong and their code quality will improve as a result.

It isn't the right thing to surface to _users_ of someone else's problematic code.  (though it does serve as a red flag proving that the owners of that code or person who pinned some dep to an old version haven't proactively tested with modern python)
Date User Action Args
2019-08-06 08:08:02gregory.p.smithsetrecipients: + gregory.p.smith, rhettinger, terry.reedy, mark.dickinson, ncoghlan, r.david.murray, njs, lukasz.langa, serhiy.storchaka, abarry, asmeurer, Eric Wieser
2019-08-06 08:08:02gregory.p.smithsetmessageid: <>
2019-08-06 08:08:02gregory.p.smithlinkissue32912 messages
2019-08-06 08:08:02gregory.p.smithcreate