#4 Python3 bytecode stale
Closed 2 years ago by tpopela. Opened 5 years ago by nanonyme.

Context, see https://gitlab.com/freedesktop-sdk/freedesktop-sdk/issues/554 (TLDR; Python 3.7 has hashed bytecode by default when SOURCE_DATE_EPOCH is set. It works perfectly in ostree. If pre-3.7 timestamp manipulations to bytecode are done, the bytecode breaks into a state where it's always invalid)

Repro: run python3 -v

you should get output that includes stuff like

# bytecode is stale for 'encodings'
# bytecode is stale for 'codecs'
# bytecode is stale for 'encodings.aliases'
# bytecode is stale for 'encodings.utf_8'
# bytecode is stale for 'encodings.latin_1'
# bytecode is stale for 'io'
# bytecode is stale for 'abc'
# bytecode is stale for '_bootlocale'
# bytecode is stale for 'site'
# bytecode is stale for 'os'
# bytecode is stale for 'stat'
# bytecode is stale for 'posixpath'
# bytecode is stale for 'genericpath'
# bytecode is stale for '_collections_abc'

Based on discussion with @walters it sounds to me more probably root cause is SOURCE_DATE_EPOCH is actually not set at all when building the source RPM's like it should so this is probably wrong place for this bug....

Metadata Update from @tpopela:
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata