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 eric.smith
Recipients Tim.Graham, abarry, brett.cannon, eric.smith, martin.panter, ncoghlan, ned.deily, r.david.murray, rhettinger, serhiy.storchaka, yan12125, yselivanov
Date 2016-09-16.14:25:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Also, I assume this is a problem with all such syntax warnings: you only see this warning/error when the file is originally compiled. Once the .pyc file exists, you'll never see a warning or error. Maybe that's okay, but it means there's a certain class of installations (such as .pyc compiled at install time) that won't be able to know these warnings exist.

This screwed me up for a while when I was developing this patch. The warnings disappeared!
Date User Action Args
2016-09-16 14:25:41eric.smithsetrecipients: + eric.smith, brett.cannon, rhettinger, ncoghlan, ned.deily, r.david.murray, martin.panter, serhiy.storchaka, yselivanov, Tim.Graham, yan12125, abarry
2016-09-16 14:25:40eric.smithsetmessageid: <>
2016-09-16 14:25:40eric.smithlinkissue28128 messages
2016-09-16 14:25:40eric.smithcreate