-
Notifications
You must be signed in to change notification settings - Fork 1.3k
lzma implementation #5717
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 our terms of service and privacy 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?
lzma implementation #5717
Conversation
This turned out surprisingly effective, about 2/3s of the tests pass, which is enough for me at the moment. The main missing parts involve a bunch of unsafe things that As a side note I also abstracted out |
c09442c
to
2bad5d2
Compare
Lots of tests are failing because they were previously blocked due to no implementation at all. |
Would you be able to squash these commits down? Ideally into one for copying the files from cpython, and one for all the rest? |
Sure |
19a43f5
to
ca2dc44
Compare
It's at 3 now, I committed things in a weird fashion so I can't get it below that. |
Signed-off-by: Ashwin Naren <[email protected]>
Signed-off-by: Ashwin Naren <[email protected]>
Signed-off-by: Ashwin Naren <[email protected]>
@@ -392,7 +392,8 @@ def __init__(self, name, mode, comptype, fileobj, bufsize, | |||
|
|||
elif comptype == "xz": | |||
try: | |||
import lzma | |||
# TODO: RUSTPYTHON remove underscore |
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.
Is this name changed to raise ImportError? What happens if it is lzma
?
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.
Yes, if left as is everything breaks because lzma is expected to be unimportable.
Based on #5709 because of the zlib abstraction.