René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"`.pyc` file in zipapp can be marked as stale if opened in a different timezone than the one it was created in","articleBody":"# Bug report\n\n### Bug description:\n\n`_get_mtime_and_size_of_source` uses localtime rather than UTC --- in a zipapp, if the pyc was created in a timezone that is different than the timezone of the computer that it is being run on, it can be marked as 'stale', even though it shouldn't be --- for example, if the source file was last modified at 3:30 EST, that 3:30 EST will be stored in the pyc file as a Unix timestamp. However, if the zipapp is then transferred to a computer running PST, the modification time of the source file will be read from the zip file as 3:30 PST in unix time (through `time.mktime`), which will obviously be different than the 3:30 EST read from the pyc file directly (since it is never passed through `time.mktime`).\n\nThis seems to be because zip files do not store timezones with mtime, so Python is forced to interpret it as local time.\n\n### CPython versions tested on:\n\n3.11, 3.13\n\n### Operating systems tested on:\n\nLinux, macOS\n\n\u003c!-- gh-linked-prs --\u003e\n### Linked PRs\n* gh-143868\n* gh-143953\n\u003c!-- /gh-linked-prs --\u003e\n","author":{"url":"https://github.com/DUOLabs333","@type":"Person","name":"DUOLabs333"},"datePublished":"2025-11-11T23:37:05.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/141431/cpython/issues/141431"}