Unable to install pymupdf 1.25.x using poetry

[sahas-si]

Description of the bug

Earlier our server(EC2 Docker python-3.11.9-slim) was running on pymupdf 1.24.0. While upgrading to 1.25.3 using poetry in docker instance, got the below errors.

[stderr]#13 25.07
[stderr]#13 25.07 - not supporting PEP 517 builds
[stderr]#13 25.07 - not specifying PEP 517 build requirements correctly
[stderr]#13 25.07 - the build requirements are incompatible with your operating system or Python version
[stderr]#13 25.07 - the build requirements are missing system dependencies (eg: compilers, libraries, headers).
[stderr]#13 25.07
[stderr]#13 25.07 You can verify this by running pip wheel --no-cache-dir --use-pep517 "pymupdf (==1.25.3)".
[stderr]#13 25.07
[stderr]#13 ERROR: process "/bin/sh -c poetry config virtualenvs.create false && poetry install --no-root --only main" did not complete successfully: exit code: 1
[stderr]------
[stderr] > [8/8] RUN poetry config virtualenvs.create false && poetry install --no-root --only main:
[stderr]25.07
[stderr]25.07 Note: This error originates from the build backend, and is likely not a problem with poetry but one of the following issues with pymupdf (1.25.3)
[stderr]25.07
[stderr]25.07 - not supporting PEP 517 builds
[stderr]25.07 - not specifying PEP 517 build requirements correctly
[stderr]25.07 - the build requirements are incompatible with your operating system or Python version
[stderr]25.07 - the build requirements are missing system dependencies (eg: compilers, libraries, headers).
[stderr]25.07
[stderr]25.07 You can verify this by running pip wheel --no-cache-dir --use-pep517 "pymupdf (==1.25.3)".
[stderr]25.07

How to reproduce the bug

1. Create a dockerfile which installs dependencies via poetry
2. Add pymupdf with version 1.25.3
3. Start the docker instance

PyMuPDF version

1.25.3

Operating system

Linux

Python version

3.11

[julian-smith-artifex-com]

Thanks for the report.

What CPU are you on, e.g. x86_64 or aarch64?

[sahas-si]

Its aarch64.

…

On Thu, Feb 27, 2025, 19:30 Julian Smith ***@***.***> wrote: Thanks for the report. What CPU are you on, e.g. x86_64 or aarch64? — Reply to this email directly, view it on GitHub <#4339 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A7RC7RKO4O3GNLCZRKEJKKD2R4LAFAVCNFSM6AAAAABX7PKZJSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOBYGA2DSNJWGY> . You are receiving this because you authored the thread.Message ID: ***@***.***> [image: julian-smith-artifex-com]*julian-smith-artifex-com* left a comment (pymupdf/PyMuPDF#4339) <#4339 (comment)> Thanks for the report. What CPU are you on, e.g. x86_64 or aarch64? — Reply to this email directly, view it on GitHub <#4339 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A7RC7RKO4O3GNLCZRKEJKKD2R4LAFAVCNFSM6AAAAABX7PKZJSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOBYGA2DSNJWGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[julian-smith-artifex-com]

Ah, there was a problem on Github's Linux-aarch64's runner when building Linux-aarch64 wheels, so they are not available in the current release.

I suspect that poetry is attempting to build PyMuPDF source, which it hasn't had to do before for you, and something is going wrong with the build.

A workaround would be to install PyMuPDF-1.25.2, for which Linux-aarch64 wheels are available.

[PyMuPDF's setup.py does support PEP 517 and works fine with pip or cibuildwheel, but it's possible it's not supporting something required by pip --use-pep517; i'm looking into this.]

[julian-smith-artifex-com]

Pip can build PyMuPDF from source with no problems with the command suggested by poetry (plus --no-binary pymupdf to force build from source):

pip wheel --use-pep517 --no-binary pymupdf "pymupdf (==1.25.3)" -vv --no-cache-dir

So this looks like a problem with Poetry itself, not PyMuPDF.