-
Notifications
You must be signed in to change notification settings - Fork 510
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
Image extraction bugs with newer versions #2369
Comments
julian-smith-artifex-com
added a commit
to ArtifexSoftware/PyMuPDF-julian
that referenced
this issue
Apr 25, 2023
julian-smith-artifex-com
added a commit
to ArtifexSoftware/PyMuPDF-julian
that referenced
this issue
Apr 25, 2023
This extends commit 3bae451, which fixed pymupdf#2348.
julian-smith-artifex-com
added a commit
that referenced
this issue
Apr 25, 2023
Re-opening because fix is not in a release yet. |
Fixed in new release 1.22.2. |
Thank you for the quick fix! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug (mandatory)
In the newer versions
1.22.0
and1.22.1
, it looks like certain image formats likepam
are not handled properly anymoreTo Reproduce (mandatory)
Running the following leads to different results with versions
1.19.6
and1.22.0
With
1.19.6
, this runs without error and printsWith
1.22.0
, the last line raises an errorand the bytes printed are very different
Your configuration (mandatory)
For example, the output of
print(sys.version, "\n", sys.platform, "\n", fitz.__doc__)
would be sufficient (for the first two bullets).Installed via
pip install pymupdf==1.22.0
The text was updated successfully, but these errors were encountered: