Closed dothinking closed 7 months ago
A fix is identified already and will lead to a new PyMuPDF version - hopefully even today.
Thanks Train! ( hope you don't me calling you "Train" - seen you use it a few times, please let me know ) . It is possible that we will have fixed some of the issues you are seeing in an imminent release of PyMuPDF.
Adding Harald & Julian here as they should be aware of the behaviour change for Rect
& Pixmap
- I think we know about the Pixmap
one already. I guess if the issues are both fixed in PyMuPDF 1.23.16 then you may want to rework this PR. @JorjMcKie , @julian-smith-artifex-com What do you think?
@jamie-lemon "Train" sounds friendly for me, as it's a name used in my college time. 😁
Regarding this PR, once released PyMuPDF 1.23.16, I just need to delete the version restriction in requirements.txt, the rest should be OK.
FYI, PyMuPDF-1.23.16 has just been released, and fixes the Pixmap issue https://github.com/pymupdf/PyMuPDF/issues/3058.
The fitz.Rect problem was introduced in 1.23.9 and fixed in 1.23.13 and later.
Hope that helps.
Some adjustments to handle the side effects of upgrading
PyMuPDF
from 1.23.8 to 1.23.14+, e.g.,fitz.Rect()
-> adjusted frompdf2docx
side. #250fitz.Pixmap()
-> downgradepymupdf
for now. https://github.com/pymupdf/PyMuPDF/issues/3058And some other tweaks, e.g., remove Github Action for publishing docs to Github page.