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 Tim.Graham, abarry, eric.smith, martin.panter, ncoghlan, ned.deily, r.david.murray, rhettinger, serhiy.storchaka, yan12125, yselivanov
Date 2016-10-03.17:13:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Eric's basic approach sounds fine to me, as it gets the traceback in the right place (i.e. blaming the code being compiled, not the code doing the import).

For beta 2, how about we just go with a plain SyntaxWarning? Since users running pre-compiled modules won't see it regardless, so it will be effectively silenced by default for end users of pre-built Python applications.
Date User Action Args
2016-10-03 17:13:28ncoghlansetrecipients: + ncoghlan, rhettinger, eric.smith, ned.deily, r.david.murray, martin.panter, serhiy.storchaka, yselivanov, Tim.Graham, yan12125, abarry
2016-10-03 17:13:28ncoghlansetmessageid: <>
2016-10-03 17:13:28ncoghlanlinkissue28128 messages
2016-10-03 17:13:28ncoghlancreate