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 lepaperwan
Recipients benjamin.peterson, lepaperwan
Date 2018-09-14.19:30:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1536953440.42.0.956365154283.issue34686@psf.upfronthosting.co.za>
In-reply-to
Content
How would you suggest going about doing that?

Without the proposed option, the alternative is leaving the build process vulnerable to environment variables potentially breaking the build process by patching configure.ac as follows:
-PYTHON_FOR_BUILD='./$(BUILDPYTHON) -E'
+PYTHON_FOR_BUILD='PYTHONHASHSEED=0 ./$(BUILDPYTHON) -E'

Otherwise all environment variables affecting the Python interpreter would need to be cleared in addition to setting PYTHONHASHSEED=0.

Without these `hacks`, making build outputs to be deterministic means fixing marshal to essentially sort elements when dumping unordered objects. Would you rather see a patch going in that direction?
History
Date User Action Args
2018-09-14 19:30:40lepaperwansetrecipients: + lepaperwan, benjamin.peterson
2018-09-14 19:30:40lepaperwansetmessageid: <1536953440.42.0.956365154283.issue34686@psf.upfronthosting.co.za>
2018-09-14 19:30:40lepaperwanlinkissue34686 messages
2018-09-14 19:30:40lepaperwancreate