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

[Donald Stufft]

On Jun 6, 2014, at 3:33 PM, Chris Angelico <rosuav at gmail.com> wrote:

> On Sat, Jun 7, 2014 at 5:11 AM, Donald Stufft <donald at stufft.io> wrote:
>> Is it really any difference in maintenance if you just stop applying updates to
>> 2.7 and switch to 2.8? If 2.8 is really just 2.7 with a new compiler then there
>> should be no functional difference between doing that and doing a 2.7.whatever
>> except all of the tooling that relies on the compiler not to change in micro
>> releases won’t suddenly break and freak out.
> 
> If the only difference between 2.7 and 2.8 is the compiler used on
> Windows, what happens on Linux and other platforms? A Python 2.8 would
> have to be materially different from Python 2.7, not just binarily
> incompatible on one platform.
> 
> ChrisA
> _______________________________________________
> Python-Dev mailing list
> Python-Dev at python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe: https://mail.python.org/mailman/options/python-dev/donald%40stufft.io

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.

-----------------
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mail.python.org/pipermail/python-dev/attachments/20140606/efb4d61c/attachment.sig>