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 vstinner
Recipients Demur Rumed, Mark.Shannon, berker.peksag, python-dev, rbcollins, serhiy.storchaka, vstinner, yselivanov
Date 2016-09-12.16:14:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1473696853.5.0.094242393737.issue27213@psf.upfronthosting.co.za>
In-reply-to
Content
> Why don't we change the magic number before b1 (if your bytecode change is already committed)?

The magic number changed many times between Python 3.5 and the future Python 3.6 beta 1. Maybe we skipped increasing this number for one bytecode change, but it should only impact the few developers who worked on the development version. In this case: just remove all ".pyc" files and it should be fine ;-)

In short: I think it's fine, don't do anything else ;-)
History
Date User Action Args
2016-09-12 16:14:13vstinnersetrecipients: + vstinner, rbcollins, Mark.Shannon, python-dev, berker.peksag, serhiy.storchaka, yselivanov, Demur Rumed
2016-09-12 16:14:13vstinnersetmessageid: <1473696853.5.0.094242393737.issue27213@psf.upfronthosting.co.za>
2016-09-12 16:14:13vstinnerlinkissue27213 messages
2016-09-12 16:14:13vstinnercreate