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 db3l
Recipients db3l, paul.moore, steve.dower, tim.golden, vstinner, zach.ware
Date 2017-11-07.10:31:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1510050677.1.0.213398074469.issue31967@psf.upfronthosting.co.za>
In-reply-to
Content
This seems to correlate with my upgrading to the latest Win10 SDK on those workers (Steve pointed out I was still getting ucrt warnings during compilation).  So they both jumped from like 10240 up to 16299.  But that's all I changed.

Interestingly I only had to fix 8.1 and 10, as 7 already had a version (15063) avoiding the warning, and it's tedious to change.  But it's not experiencing the linking problem.

I could swear I recall past link/rc problems, but my searching (and memory) are failing me at the moment.  But I wonder if that's why I had left these two workers back at 10240, or if I had some local fix in place.
History
Date User Action Args
2017-11-07 10:31:17db3lsetrecipients: + db3l, paul.moore, vstinner, tim.golden, zach.ware, steve.dower
2017-11-07 10:31:17db3lsetmessageid: <1510050677.1.0.213398074469.issue31967@psf.upfronthosting.co.za>
2017-11-07 10:31:17db3llinkissue31967 messages
2017-11-07 10:31:17db3lcreate