[Python-Dev] PEP 552: deterministic pycs
Benjamin Peterson
benjamin at python.org
Thu Sep 7 17:08:58 EDT 2017
More information about the Python-Dev mailing list
Thu Sep 7 17:08:58 EDT 2017
- Previous message (by thread): [Python-Dev] PEP 552: deterministic pycs
- Next message (by thread): [Python-Dev] PEP 552: deterministic pycs
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, Sep 7, 2017, at 14:00, Antoine Pitrou wrote: > On Thu, 07 Sep 2017 13:39:21 -0700 > Benjamin Peterson <benjamin at python.org> wrote: > > Hello, > > I've written a short PEP about an import extension to allow pycs to be > > more deterministic by optional replacing the timestamp with a hash of > > the source file: https://www.python.org/dev/peps/pep-0552/ > > Why isn't https://github.com/python/cpython/pull/296 a good enough > solution to this problem? It has a simple implementation, and requires > neither maintaining two different pyc formats nor reading the entire > source file to check whether the pyc file is up to date. The main objection to that model is that it requires modifying source timestamps, which isn't possible for builds on read-only source trees. This proposal also allows reproducible builds even if the files are being modified in an edit-run-tests cycle.
- Previous message (by thread): [Python-Dev] PEP 552: deterministic pycs
- Next message (by thread): [Python-Dev] PEP 552: deterministic pycs
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list