[issue31595] Preferring MSVC 2017 in Python 3.6.x new minor releases

xoviat added the comment: @zooba Since you mention it, I agree with that proposal. But currently we have core developers contributing to distutils and @jaraco contributing to setuptools. @jaraco is quite competent, but I doubt that he would be able to maintain an independent fork of distutils

[issue31595] Preferring MSVC 2017 in Python 3.6.x new minor releases

Changes by Steve Dower : -- resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Python-

[issue31595] Preferring MSVC 2017 in Python 3.6.x new minor releases

Steve Dower added the comment: Let me hop in my time machine and fix that for you: https://github.com/python/cpython/pull/3425 (FWIW, I think it makes *much* more sense for setuptools to fix this by simply forking all of distutils and never looking back. But since we don't live in that world

[issue31595] Preferring MSVC 2017 in Python 3.6.x new minor releases

Zachary Ware added the comment: 3.5 is in security-fix-only mode, so it will not receive such an update. 3.6 is up to Ned and Steve. -- assignee: -> steve.dower components: +Windows nosy: +ned.deily, paul.moore, steve.dower, tim.golden, zach.ware title: Preferring MSVC 2017 in Python