strict_timestamps for PyZipFile

[sakcheen]

BPO	45140

^{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 2021-09-08.17:36:10.345>
labels = ['library', '3.9']
title = 'strict_timestamps for PyZipFile'
updated_at = <Date 2021-09-08.17:36:10.345>
user = 'https://bugs.python.org/sakcheen'

bugs.python.org fields:

activity = <Date 2021-09-08.17:36:10.345>
actor = 'sakcheen'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2021-09-08.17:36:10.345>
creator = 'sakcheen'
dependencies = []
files = []
hgrepos = []
issue_num = 45140
keywords = []
message_count = 1.0
messages = ['401417']
nosy_count = 1.0
nosy_names = ['sakcheen']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue45140'
versions = ['Python 3.9']

[sakcheen]

#8270

Above fix solved the problem with pre-1980 files for regular ZipFile, but I still have issues when using PyZipFile object.

https://docs.python.org/3.11/library/zipfile.html#pyzipfile-objects

I would be glad if strict_timestamps was added to PyZipFile as well.

The documentation of PyZipFile also states that PyZipFile has the same parameters as ZipFile with the addition of one extra. If this issue can't be fixed in code, at least the documentation should be updated to reflect this is not longer true.

[StanFromIreland]

The current behavior contradicts the documentation:

The PyZipFile constructor takes the same parameters as the ZipFile constructor, and one additional parameter, optimize.