Python 3 runs builds against the old MSVC (14.0) and the current one (14.1). I’m happy to fully drop support for the older one and remove those builds, but there was a bit of push back when first proposed. (Both toolsets produce binary compatible outputs, but the newer one has better library/compiler support and we may break people who don’t want to upgrade if we use it.)
Top-posted from my Windows phone From: Brett Cannon Sent: Tuesday, January 16, 2018 11:49 To: Antoine Pitrou Cc: python-committers Subject: Re: [python-committers] AppVeyor is now required to pass on PRs On Mon, 15 Jan 2018 at 14:42 Antoine Pitrou <anto...@python.org> wrote: Hi Brett, Stability doesn't appear to be a problem, but we have much less parallelism on AppVeyor than we do on Travis-CI. This may make waiting times longer than they used to be. Apparently 3.6 builds (and perhaps 2.7) trigger two sequential AppVeyor jobs: https://ci.appveyor.com/project/python/cpython/build/3.6build10551 If the wait times become an issue for anyone then let me know and we can re-evaluate the situation. -Brett Regards Antoine. Le 10/01/2018 à 21:45, Brett Cannon a écrit : > I just switched it on to help make sure we don't break on Windows just > before hitting beta. If it turns out AppVeyor isn't stable enough I will > switch it back off. > > > _______________________________________________ > python-committers mailing list > python-committers@python.org > https://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://www.python.org/psf/codeofconduct/ > _______________________________________________ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
_______________________________________________ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
