➜

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 phelix
Recipients docs@python, ezio.melotti, paul.moore, phelix, steve.dower, tim.golden, willingc, zach.ware
Date 2015-09-28.08:05:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1443427518.11.0.403449402832.issue25255@psf.upfronthosting.co.za>
In-reply-to
Content 
A description of the build and release process for CPython binaries (e.g. for Windows) would be great. Maybe I am missing something? I could not find any information other than the 14 years old PEP 101 which says: "Notify the experts that they can start building binaries." 

E.g. how is it ensured there are no backdoors in the binaries?

Background: For the Namecoin project we are currently discussing the potential necessity of reproducible builds.
History
Date User Action Args
2015-09-28 08:05:18phelixsetrecipients: + phelix, paul.moore, tim.golden, ezio.melotti, docs@python, zach.ware, steve.dower, willingc
2015-09-28 08:05:18phelixsetmessageid: <1443427518.11.0.403449402832.issue25255@psf.upfronthosting.co.za>
2015-09-28 08:05:18phelixlinkissue25255 messages
2015-09-28 08:05:17phelixcreate