gh-130120: Prevent str(zipfile.Path) from raising exception on io.BytesIO-input
#130381
+11
−2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ot.filename is None
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here are some small updates to
zipfile.Pathto prevent them from raising exceptions when Path-objects that are based on in-memory zipfiles are printed.I set the printed filename to
:memory:to mirror the behaviour of in-memory sqlite3 databases. However, it may also make sense to set the name to\0(or include\0in the name) to make it abundantly clear that this is no file.zipfile.Pathhas only partial compatibilityio.BytesIO#130120