the-knights-who-say-ni · GitHub

warsaw

@vstinner vstinner changed the title allow for reproducible builds of python packages support SOURCE_DATE_EPOCH env var in pycompile (allow for reproducible builds of python packages)

Mar 2, 2017

vstinner

@vstinner vstinner changed the title support SOURCE_DATE_EPOCH env var in pycompile (allow for reproducible builds of python packages) support SOURCE_DATE_EPOCH env var in py_compile (allow for reproducible builds of python packages)

Mar 2, 2017

@bmwiedemann bmwiedemann changed the title support SOURCE_DATE_EPOCH env var in py_compile (allow for reproducible builds of python packages) bpo-29708: support SOURCE_DATE_EPOCH env var in py_compile (allow for reproducible builds of python packages)

Mar 3, 2017

@bmwiedemann

Merged

warsaw

@bmwiedemann

@bmwiedemann

@FRidh FRidh mentioned this pull request

Mar 17, 2017

Closed

to allow for reproducible builds of python packages
See https://reproducible-builds.org/ for why this is good
and https://reproducible-builds.org/specs/source-date-epoch/
for the definition of this variable.
Background:
In some distributions like openSUSE, binary rpms contain precompiled .pyc files.
And packages like amqp or twisted dynamically generate .py files at build time
so those have the current time and that timestamp gets embedded
into the .pyc file header.
When we then adapt file timestamps in rpms to be constant,
the timestamp in the .pyc header will no more match
the .py timestamp in the filesystem.
The software will still work, but it will not use the .pyc file as it should.

@bmwiedemann

eli-schwartz

@brettcannon

brettcannon

Closed

Closed

akruis added a commit to akruis/cpython that referenced this pull request

Aug 1, 2021
It is now possible to cross-compile Stackless for Windows on ARM and ARM64.

Closed

@gicmo gicmo mentioned this pull request

Feb 7, 2022

Merged

Closed

jaraco pushed a commit that referenced this pull request

Dec 2, 2022

mcepl added a commit to openSUSE-Python/cpython that referenced this pull request

Apr 3, 2024
Created by Bernhard M. Wiedemann <bmwiedemann@suse.de> -- gh#python#296

mcepl added a commit to openSUSE-Python/cpython that referenced this pull request

Apr 4, 2024
Created by Bernhard M. Wiedemann <bmwiedemann@suse.de> -- gh#python#296
Patch: 0001-allow-for-reproducible-builds-of-python-packages.patch

mcepl added a commit to openSUSE-Python/cpython that referenced this pull request

Apr 4, 2024
Created by Bernhard M. Wiedemann <bmwiedemann@suse.de> -- gh#python#296
Patch: 0001-allow-for-reproducible-builds-of-python-packages.patch

mcepl pushed a commit to openSUSE-Python/cpython that referenced this pull request

Apr 4, 2024
Code is originally from gh#python#296 (never released in
this form).
Patch: 0001-allow-for-reproducible-builds-of-python-packages.patch

mcepl pushed a commit to openSUSE-Python/cpython that referenced this pull request

Apr 4, 2024
See https://reproducible-builds.org/ for why this is good idea
and https://reproducible-builds.org/specs/source-date-epoch/
for the definition of this variable.
Background:
In some distributions like openSUSE, binary rpms contain precompiled .pyc files.
And packages like amqp or twisted dynamically generate .py files at build time
so those have the current time and that timestamp gets embedded
into the .pyc file header.
When we then adapt file timestamps in rpms to be constant,
the timestamp in the .pyc header will no more match
the .py timestamp in the filesystem.
The software will still work, but it will not use the .pyc file as it should.
Original version which doesn't force hashed *.pyc files
Code is originally from gh#python#296 (never released in
this form).
Patch: 0001-allow-for-reproducible-builds-of-python-packages.patch

Read the original on github.com ↗