Alexander Sturm <ast...@hbk.com> added the comment: As mentioned, the code is compiled correctly by VS2017 - both in 3.5.5 and 3.6.5. So I cannot reproduce the issue with Python 3.6.5.
Would it be possible to switch the default platform toolset used to compile Python 3.5 in the next source release to v141? According to Microsoft, it should be ABI compatible with v140: https://blogs.msdn.microsoft.com/vcblog/2017/03/07/binary-compatibility-and-pain-free-upgrade-why-moving-to-visual-studio-2017-is-almost-too-easy/ If that's out of the question, I agree that there's probably not much that can be done here - other then maybe locally disabling optimizations for that loop. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33232> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
