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 MartyMacGyver
Recipients MartyMacGyver, ned.deily, serhiy.storchaka, steve.dower, terry.reedy, tim.golden, zach.ware
Date 2015-04-19.21:14:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1429478051.01.0.163148337353.issue23982@psf.upfronthosting.co.za>
In-reply-to
Content
Thank you. Before going down the road of revising PEP 101 (which appears to be very non-trivial despite the simple (and certainly always present) data involved), I'd like to know: is version information about the pre-compiled Windows binaries (of which this is one) already being captured anywhere else publically visible on a per-release or per-build basis? It's useful that such binaries exist given Windows' unique requirements versus other systems, but are these binaries themselves documented anywhere as they are updated (e.g., how to re-create them)? Such a source of truth would simplify that revision request.
History
Date User Action Args
2015-04-19 21:14:11MartyMacGyversetrecipients: + MartyMacGyver, terry.reedy, tim.golden, ned.deily, zach.ware, serhiy.storchaka, steve.dower
2015-04-19 21:14:11MartyMacGyversetmessageid: <1429478051.01.0.163148337353.issue23982@psf.upfronthosting.co.za>
2015-04-19 21:14:10MartyMacGyverlinkissue23982 messages
2015-04-19 21:14:10MartyMacGyvercreate