chore: depend on cpython to ensure GIL-enabled Python - #1158
Merged
Conversation
CMake requires cpython on arm platforms to properly detect the Python interpreter. Add it to both linux and mac dev environments.
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Starting with Python 3.14, conda-forge ships the free-threaded (no-GIL) build as the default python package. CMake's
find_package(Python)does not recognize this freethreading variant by default, so an ARTS configuration against it fails or selects an interpreter our nanobind-based bindings cannot use. We require the traditional GIL-enabled interpreter.The clean fix would be to depend on the
python-gilpackage, which explicitly pins the GIL build; however, that package does not exist for Python versions below 3.14, so adding it would break environment creation on 3.12 and 3.13. Depending oncpythoninstead achieves the same effect. It pulls in the GIL-enabled CPython interpreter while remaining installable across all currently supported Python versions, making it a workaround that works universally rather than only on 3.14+.