Home Original page

[Python-Dev] Moving Python 3.5 on Windows to a new compiler

Chris Angelico rosuav at gmail.com
Fri Jun 6 21:46:48 CEST 2014 
On Sat, Jun 7, 2014 at 5:36 AM, Donald Stufft <donald at stufft.io> wrote:
> Well it’d contain bug fixes and whatever other sorts of things you’d put
> into a 2.7.whatever release. So they’d still want to upgrade to 2.8 since
> that’ll have bug fixes.

But it's not a potentially-breaking change. For example, on Debian
Wheezy, there are a huge number of packages that depend on "python (<<
2.8)", because they expect Python 2.7 and *not* Python 2.8. A newer
version 2.7 will satisfy that; a version 2.8 won't, because it's
entirely possible that 2.8 will have something that's significantly
different. That's what version numbers mean; Python follows the
standard three-part convention, where you upgrade automatically only
within the last part of the number.

ChrisA
More information about the Python-Dev mailing list