Repository navigation
Documentation for tarfile has ambigouous references for releases #104638
Description
Activity
I don't see a way to add labels to this issue, but it should have 3.11 label attached.
The text as written is correct: this is the anticipated behavior in 3.12 and 3.14. cc @encukou for tarfile filters.
Do you have suggestions for how to make this clearer?
I guess I don't have a better wording to suggest. When I saw that release 3.13 was skipped, I expected that there was some kind of mistake.
Perhaps instead of
Python 3.12+, make itPython 3.12 and 3.13?Reacted by sunmy2019, John Canning and Robert O'Shea@JMCanning78 Would you like to make a PR with @zware's suggestion?
@JMCanning78 are you working on this issue? If not @hugovk can I take it?
@hadrizi, thanks for asking. No I am not working on this issue.
I think this issue is no longer relevant after the changes in #122002
Documentation
The documentation for
TarFile.extraction_filterunder "New in version 3.11.4." it states:"In Python 3.12+, leaving extraction_filter=None will emit a DeprecationWarning.
In Python 3.14+, leaving extraction_filter=None will cause extraction methods to use the data filter by default."
Perhaps this is a forward looking comment about behavior to expect in Python releases 3.12 and 3.14, but I suspect that they should instead be something like "Python 3.11.2+" and "Python 3.11.4+" to document existing behavior.
Linked PRs
TarFile.extraction_filterfuture release references more clear #109908