Am 07.06.14 01:01, schrieb Steve Dower: > We keep the VS 2010 files around and make sure they keep working. > This is the biggest risk of the whole plan, but I believe that > there's enough of a gap between when VS 14 is planned to release > (which I know, but can't share) and when Python 3.5 is planned (which > I don't know, but have a semi-informed guess).
By "keep around", I'd be fine with "in a subdirectory of PC". PCbuild should either switch for sure, or not switch at all. People had proposed to come up with a "PCbuildN" directory (N=10, N=14, or whatever) to maintain two build environments simultaneously; I'd be -1 on such a plan. There needs to be one official toolset to build Python X.Y with, and it needs to be either VS 2010 or VS 2014, but not both. > Is Python 3.5b1 being built with VS 14 RC (hypothetically) a blocking > issue? Do we need to resolve that now or can it wait until it > happens? It's up to the release manager, but I'd personally see it as a blocking issue: we shouldn't use a beta compiler for the final release, and we shouldn't switch compilers (back) after b1. The RM *could* opt to bet on VS 14 RTM appearing before 3.5rc1 is released (or otherwise blocking rc1 until VS 14 is released); I would consider this risy, but possibly worth it. We certainly don't need to resolve this now. We should discuss it again when the release schedule for 3.5 is proposed. Regards, Martin _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
