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 lukasz.langa
Recipients Eric Appelt, barry, brett.cannon, doko, eric.snow, lukasz.langa, ncoghlan, petr.viktorin, serhiy.storchaka
Date 2017-02-13.04:45:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1486961112.44.0.354044874696.issue29514@psf.upfronthosting.co.za>
In-reply-to
Content
I commented on the original issue where the magic number was changed. This broke the world at work for me. Our distribution mechanism for Python programs is zipped bundles of .pyc and .so files, the optimized variant doesn't keep .py files around. So suddenly otherwise correct bundles were refusing to start. Better yet, since the rollout of Python is staged and takes a while to do safely, new packages started appear with the new magic number that were refusing to start on 3.5.0. This was not a fun day :)

So, while I understand Brett's and Serhiy's reasoning, I'd be very careful about ever bumping magic numbers in minor releases again, and definitely communicate loudly if doing so.

Oh, if you're wondering why I even hit this problem before 3.5.3: since 3.5.2 had a few regressions we couldn't live with, I released 3.5.2+ from the latest commit on the 3.5 branch at the time (after checking the buildbots, running tests on our own, etc.). I repeated this feat with 3.6.0+ and again hit a thing that would likely upset some people in 3.6.1 (see #29519) but this time decided to patch it instead of just complaining ;)
History
Date User Action Args
2017-02-13 04:45:12lukasz.langasetrecipients: + lukasz.langa, barry, brett.cannon, doko, ncoghlan, petr.viktorin, eric.snow, serhiy.storchaka, Eric Appelt
2017-02-13 04:45:12lukasz.langasetmessageid: <1486961112.44.0.354044874696.issue29514@psf.upfronthosting.co.za>
2017-02-13 04:45:12lukasz.langalinkissue29514 messages
2017-02-13 04:45:11lukasz.langacreate