phelix added the comment:
Thank you all for your responses.
> Having read your link [2] above (at least briefly), it seems the aim is to
> compare hashes of builds from multiple people to verify that nobody
> maliciously modified the binaries.
Exactly. Also it might protect t
phelix added the comment:
@Brett: Thanks for the info, I had not noticed PEP 101 had been updated.
@Paul: Ah, I had not found PCBuild/readme.txt yet. I did look at the devguide
but I got the impression it was mostly meant for debug builds.
> Basically through trusting the people who prod
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
