Repository navigation
Declare external build dependencies using PEP 725 - #1091
Open
garth-wells wants to merge 1 commit into
Open
garth-wells wants to merge 1 commit into
garth-wells wants to merge 1 commit into
Conversation
jhale
reviewed
Oct 17, 2026
|
|
||
| ### External dependency metadata | ||
|
|
||
| Both `pyproject.toml` files declare non-Python build dependencies in an |
Member
There was a problem hiding this comment.
Ask LLM to cut this back, not needed.
This branch has not been deployed
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.
Closes #986.
PEP 735 dependency groups were implemented in #1060. Add the remaining external dependency declarations using the draft PEP 725 format and PEP 804 identifiers: CMake and a C++ compiler for both build layouts, BLAS/LAPACK for the combined build, and the installed Basix C++ library for the Python-only build. CMake continues to enforce C++20 support.
Document the build/host distinction and correct the claim that pip fetches all C++ dependencies. Both external-dependency PEPs remain drafts; this makes requirements available in source metadata without promising automatic system-package installation. The Basix C++ GitHub identifier is valid but is not yet in the prototype central registry, so ecosystem mappings may need to be supplied separately.
Validation: