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 jpe
Recipients jpe, martin.panter, python-dev, rhettinger, serhiy.storchaka
Date 2016-08-10.19:10:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Should the bytecode magic number be bumped in the 3.5 branch?  This breaks .pyc / .pyo binary compatibility for python 3.5.  As far as I can tell this has never been done before in a release after the major.minor.0 final release.

This patch has made its way into debian's python 3.5 and I've gotten a bug report because of it for an app distributed without python source.

Looking at the 3.5.2 tarball, it does not look like the change was included in 3.5.2.  If the magic number is bumped in 3.5, the comment should be changed to reflect that it changes in 3.5.3 and not in 3.5.2
Date User Action Args
2016-08-10 19:10:39jpesetrecipients: + jpe, rhettinger, python-dev, martin.panter, serhiy.storchaka
2016-08-10 19:10:39jpesetmessageid: <>
2016-08-10 19:10:39jpelinkissue27286 messages
2016-08-10 19:10:39jpecreate