Message 314989 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	asturm
Recipients	asturm, larry, paul.moore, steve.dower, tim.golden, zach.ware
Date	2018-04-05.15:10:58
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1522941058.91.0.682650639539.issue33232@psf.upfronthosting.co.za>
In-reply-to

Content
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.

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.

History
Date	User	Action	Args
2018-04-05 15:10:58	asturm	set	recipients: + asturm, paul.moore, larry, tim.golden, zach.ware, steve.dower
2018-04-05 15:10:58	asturm	set	messageid: <1522941058.91.0.682650639539.issue33232@psf.upfronthosting.co.za>
2018-04-05 15:10:58	asturm	link	issue33232 messages
2018-04-05 15:10:58	asturm	create