[Python-Dev] 3.5 release schedule PEP (original) (raw)
Donald Stufft donald at stufft.io
Wed Sep 24 04🔞28 CEST 2014
- Previous message: [Python-Dev] 3.5 release schedule PEP
- Next message: [Python-Dev] 3.5 release schedule PEP
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sep 23, 2014, at 10:14 PM, Steve Dower <Steve.Dower at microsoft.com> wrote:
"This new compiler has the incredibly awesome feature of being forwards compatible right? Like in 10 years stuff compiled with a newer compiler will still work?" That's the promise at least :) All the macros that leaked implementation details (like file descriptors) are now isolated so if they change it won't break existing applications. It'll still be possible for newer compiler versions to break them, but the design now obviously discourages it. There's also an official guarantee, so if it is broken in future it'll be treated as a bug. As much as I'd love to make solid promises, I can only pass on the promises that were made to me. But yes, we should have forward compatibility with later MSVC versions, which will help avoid the situation where it's hard to get hold of the right compiler... Top-posted from my Windows Phone
Yea I think it makes incredible sense to aim for it then, even if it makes things slip.
Donald Stufft PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20140923/43384dff/attachment-0001.html>
- Previous message: [Python-Dev] 3.5 release schedule PEP
- Next message: [Python-Dev] 3.5 release schedule PEP
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]