Build all python package dependencies #1013
Open
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.
Build all python dependencies from source
Summarize your change.
After fixing ABI compatibility issues with OTIO arising from the fact that we are building our own custom python, I checked the other packages and there are indeed others that also have binary components (PyOpenGL_accelerate, pydantic, and cryptography).
Because of this, we should just always build the packages from source with the same compiler we use to build python, and we can do that using the --no-binary option from pip. Although this might be a little bit slower, it will ensure that any package with binary components won't have ABI compatibility issues and for pure python packages it has no effect anyway.
Describe the reason for the change.
ABI safety
Describe what you have tested and on which operating system.
Built on Mac OS 26.1.