-
Notifications
You must be signed in to change notification settings - Fork 511
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
release 1.23.0 not MacOS-arm64 compatible #2613
Comments
Thanks for reporting this. Can you do In 1.23.0, the PyMuPDF wheel lists a new wheel I'm not familiar with what [Using two wheels in this way saves space on pypi.org, because we end up with just one PyMuPDFb wheel (containing the large MuPDF binaries) per OS.] |
I've tried |
This is odd, it works fine on other platforms. It looks like something may be installing a If you could you do the following, it might allow us to figure out what's going on.
|
Can confirm I am also having this issue. Did a pip cache purge, deleted the venv, tried install fitz on its own, etc. For pip install -vv PyMuPDF | tee out
|
It looks like some binaries within PyMuPDF 1.23.0-*macosx_11_0_arm64.whl wheels have been built incorrectly with a native x86_64 compiler instead of a cross compiler that targets arm64. Apologies for this. We should be able to make a fixed release soon. |
I've have a test wheel that may fix the problem. The wheel is for MacOS, arm64 and Python-3.11. It has been uploaded to test.pypi.org, and can be tested with:
Please let me know whether this works for you. |
We've made a new release, PyMuPDF-1.23.1, which hopefully fixes this issue. But we are currently unable to test MacOS arm64 wheels directly, so if people here could report how they get on with the new release, that would be very much appreciated. |
Here is Claude summary of my testing: Summary: Getting an architecture mismatch error when trying to import PyMuPDF on M1 Mac Repro steps:
Error: Both installation methods produce the same import error:
Environment details:
Attaching pip install log and screenshot showing architecture mismatch. Claude was better summarizing than my first attempt :) |
Thanks for checking this, i'll carry on investigating what's going wrong. |
I also encountered this issue, hopefully can solve it soon. |
I've made some progress i think. This wheel works for me on a macos-arm64 gcc cfarm machine: http://ghostscript.com/~julian/PyMuPDF-1.23.1-cp39-none-macosx_11_0_arm64.whl (I only have a wheel for Python-3.9 at the moment, more on Monday.) |
Here's a second test wheel now, for Python-3.11 on macos-arm64: https://ghostscript.com/~julian/PyMuPDF-1.23.1-cp311-none-macosx_11_0_arm64.whl (To test it, download to local directory and install with Note that currently i only have access to Python-3.9 on macos-arm64, so this wheel is untested. |
I meet some problems when import. At last install the latest pre-release version resolve it. |
Fixed in release 1.23.2. |
Yes. Thank you. This seems to fix the ARCH error. However, when I run 1.23.2 against
Does 1.23.2 not support OCR? I could run this file against 1.22. |
Not sure "+1"s are useful here, but this fixes my macOS arm64 builds, thanks for quick response. Downstream reference: https://gitlab.com/plom/plom/-/merge_requests/2217/ |
This is fixed in PyMuPDF-1.23.3. |
fixes problem with pymupdf/PyMuPDF#2613 (comment)
Please provide all mandatory information!
Using os x Ventura 13.4.1
installs fine however when running you receive :
backing down to
restores a working version
The text was updated successfully, but these errors were encountered: