New submission from phelix bitcoin:

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.

----------
assignee: docs@python
components: Build, Devguide, Documentation, Windows
messages: 251753
nosy: docs@python, ezio.melotti, paul.moore, phelix bitcoin, steve.dower, 
tim.golden, willingc, zach.ware
priority: normal
severity: normal
status: open
title: Security of CPython Builds
type: enhancement

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue25255>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to