-
-
Notifications
You must be signed in to change notification settings - Fork 33k
Note SOURCE_DATE_EPOCH
support in ZipFile.writestr()
#139396
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Ok, I'm proposing to remove that note from the 'A new type of interpreter' section, and I've also made the A |
SOURCE_DATE_EPOCH
support in ZipFile.writestr()
Finished, thank you! |
Doc/library/zipfile.rst
Outdated
.. versionchanged:: 3.14 | ||
Now respects :envvar:`SOURCE_DATE_EPOCH` environment variable. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the text can be improved here. The sentence lacks an object, but more importantly we don't say what has actually changed in the method's behaviour if SDE is set.
A
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
.. versionchanged:: 3.14
:meth:`.ZipFile.writestr` now respects the :envvar:`SOURCE_DATE_EPOCH` environment variable. If set, it uses this value as the modification timestamp for the file written into the ZIP archive.
This will better?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated
SOURCE_DATE_EPOCH
support in ZipFile.writestr()
SOURCE_DATE_EPOCH
support in ZipFile.writestr()
No description provided.