Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork32k
bpo-24301: Do not fail when gzip files have trailing garbage#29847
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 ourterms of service andprivacy 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 PR is stale because it has been open for 30 days with no activity. |
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.
Could you add to docs, please?
I think its important users know what to expect. Does't need much, similar to what you have in NEWS.
@MaxwellDupre I added some |
python-cla-botbot commentedApr 18, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Apparently the
gzip
command line utility and several others display the same behaviour. Python failing here is unexpected.The code was adapted so that trailing garbage emits a warning (just like the gzip cli). The first member is still checked for a correct magic number.
https://bugs.python.org/issue24301