Docs: Refer to pymupdf instead of fitz for python module #4239
Conversation
This file contains hidden or 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
Contributor
|
All contributors have signed the CLA ✍️ ✅ |
Contributor
Author
|
I have read the CLA Document and I hereby sign the CLA |
JorjMcKie
approved these changes
Jan 21, 2025
Collaborator
|
Many thanks for this PR, it's now merged. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
I was searching for layout-preserving processing on PDFs and Google pushed Discussion #1131 at the top of the results.
I went ahead and downloaded the fitzcli.py from the PyMuPDF-Utilities repo.
I couldn't use the module with
python -m fitzand while I was looking at the documentation, I noticed that it was referring tofitzinstead ofpymupdfwhich was a bit confusing at first glancePyMuPDF version:
1.25.1