fix: pymupdf version

[charlesmindee]

This PR allows the PyMuPDF version to be 1.18.15 for in-house compatibility issues.

Any feedback is welcome!

[codecov]

Codecov Report

Merging #673 (f1f0b0b) into main (1dad108) will increase coverage by 0.15%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #673      +/-   ##
==========================================
+ Coverage   96.17%   96.32%   +0.15%     
==========================================
  Files         117      117              
  Lines        4472     4466       -6     
==========================================
+ Hits         4301     4302       +1     
+ Misses        171      164       -7     

Flag	Coverage Δ
unittests	96.32% <ø> (+0.15%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
...dels/detection/differentiable_binarization/base.py	91.30% <0.00%> (-0.63%)	⬇️
doctr/datasets/cord.py	97.43% <0.00%> (ø)
doctr/datasets/funsd.py	96.87% <0.00%> (ø)
doctr/datasets/sroie.py	94.87% <0.00%> (ø)
doctr/datasets/doc_artefacts.py	94.11% <0.00%> (ø)
doctr/datasets/detection.py	97.05% <0.00%> (+0.18%)	⬆️
doctr/models/detection/linknet/base.py	89.02% <0.00%> (+1.02%)	⬆️
doctr/models/detection/linknet/pytorch.py	98.03% <0.00%> (+1.77%)	⬆️
doctr/models/detection/linknet/tensorflow.py	100.00% <0.00%> (+3.48%)	⬆️
doctr/datasets/ocr.py	92.00% <0.00%> (+4.00%)	⬆️
... and 1 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1dad108...f1f0b0b. Read the comment docs.

[fg-mindee]

Before changing this, we need to ensure that version 1.18.11 is compatible. Because here enlarging the constraint will always install (in the CI) the latest, meaning 1.18.15. Can you confirm that you can run all unittests in 1.18.11? 🙏

[charlesmindee]

It is indeed not working with 1.18.11, it works since the 1.18.13

[fg-mindee]

Perfect thanks! Two things:

• let's do the same type of check when we want to update some dependency specifiers
• if you have a clear idea of the justification of the upper & lower bounds of the specifier, could you add an inline comment in the setup.py? (that will be easier for next time)

[fg-mindee]

Perfect thanks!