[issue29514] Add a test case that prevents magic number changes in minor releases

[Mark Dickinson]

Mark Dickinson added the comment:

[Nick]
> "Requires a mass rebuild of all the Python packages in the distro to get things working properly again" is again a major concern for what's nominally a low impact maintenance update.

With my Enthought developer hat on, I'd like to second this comment. We'll shortly be shipping Python 3.5.2 in Enthought Canopy, and this bytecode change presents us with a major issue to resolve (internal discussion about how to do so is ongoing). If/when we make 3.5.3 available, and the user upgrades their core Python, all user-installed 3rd party packages become semi-broken, and we potentially need to ask the user to upgrade many hundreds of packages. (We also need to rebuild and re-test all those packages for our own repository, which is a time-consuming process.)

[Łukasz]
> I'd be very careful about ever bumping magic numbers in minor releases again, and definitely communicate loudly if doing so.

Also seconded.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29514>
_______________________________________