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 larry
Recipients larry, paul.moore, scw, steve.dower, tim.golden, zach.ware
Date 2016-09-07.22:50:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1473288603.2.0.427895196552.issue27995@psf.upfronthosting.co.za>
In-reply-to
Content
I talked this over with Steve Dower, the current "platform expert" for Windows.  As he points out: the 3.4 Windows build is effectively unsupported.  The Windows platform expert for Python 3.4 resigned from core Python development.  Also, of course, all future Python 3.4 releases will be source releases only.  In short: if you make this change, you'd probably be the only person who would test it before it goes out the door.

But!  We still have Windows buildbots that can build Python 3.4.  And, since you're using a version of OpenSSL that we have checked in (on svn.python.org), it is theoretically possible to run this build on the buildbots.

So!  My price is: since you're going to have to coordinate with someone with the commit bit for this, you (and they) need to get this to pass on a Python buildbot.  Create a server-side clone, check in the change, and kick off a custom build.  When you get it working, post the results here, and after that you'll have my blessing to check this in to 3.4.
History
Date User Action Args
2016-09-07 22:50:03larrysetrecipients: + larry, paul.moore, tim.golden, zach.ware, steve.dower, scw
2016-09-07 22:50:03larrysetmessageid: <1473288603.2.0.427895196552.issue27995@psf.upfronthosting.co.za>
2016-09-07 22:50:03larrylinkissue27995 messages
2016-09-07 22:50:03larrycreate