Repository navigation
adding mtime option to gzip open() #91372
Description
| BPO | 47216 |
|---|---|
| Nosy | @ellaellela |
| PRs |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = None
created_at = <Date 2022-04-04.17:47:01.278>
labels = ['type-feature', 'library', '3.11']
title = 'adding mtime option to gzip open()'
updated_at = <Date 2022-04-04.17:48:26.627>
user = 'https://github.com/ellaellela'bugs.python.org fields:
activity = <Date 2022-04-04.17:48:26.627>
actor = 'ellaellela'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2022-04-04.17:47:01.278>
creator = 'ellaellela'
dependencies = []
files = []
hgrepos = []
issue_num = 47216
keywords = ['patch']
message_count = 1.0
messages = ['416685']
nosy_count = 1.0
nosy_names = ['ellaellela']
pr_nums = ['32310']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue47216'
versions = ['Python 3.11']
Activity
ellaellela commented on Apr 4, 2022
init of class GzipFile has mtime as an optional argument, but open() function does not.
When using open(), mtime will always be set to the current time and so far there was no way of fixing it to a specific timestamp.
In case two people would tar.gz the same file and take its sha, the shas would be different. With an option to fix the mtime, they could have a unique sha.
PR containing code change and the tests is already ready.
Remove timestamp from gzip to achieve r-b
Remove timestamp from gzip to achieve r-b
Remove timestamp from gzip to achieve r-b
gh-91372: Add mtime to gzip.open() (GH-32310)
pythongh-91372: Add mtime to gzip.open() (pythonGH-32310)
pythongh-91372: Add mtime to gzip.open() (pythonGH-32310)