Removed support for building separate pymupdfb and pymupdfd wheels.#5039
Merged
Conversation
We used to build separate wheels:
pymupdf: pymupdf code without mupdf libraries.
pymupdfb: mupdf libraries.
pymupdfd: mupdf headers and windows .d library stubs.
This was to reduce the overall size of our wheels on pypi.org when we had a
separate wheel for each supported python version - it meant that each of these
wheels could share the same (large) pymupdfb wheel.
But for a while now we've been using py_limited_api to produce a single pymupdf
wheel for each OS that works on all python versions.
So we don't need the (fairly copmlex) support for building pymupdfb etc, and
it's unlikely that we will need it in the future either.
JorjMcKie
approved these changes
Jul 2, 2026
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 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.
We used to build separate wheels:
pymupdf: pymupdf code without mupdf libraries.
pymupdfb: mupdf libraries.
pymupdfd: mupdf headers and windows .d library stubs.
This was to reduce the overall size of our wheels on pypi.org when we had a separate wheel for each supported python version - it meant that each of these wheels could share the same (large) pymupdfb wheel.
But for a while now we've been using py_limited_api to produce a single pymupdf wheel for each OS that works on all python versions.
So we don't need the (fairly copmlex) support for building pymupdfb etc, and it's unlikely that we will need it in the future either.