Repository navigation
chore: move metadata to pyproject.toml - #245
Merged
Merged
Conversation
Assisted-by: ClaudeCode:claude-opus-5-5
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
1 participant
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.
🤖 AI text below 🤖
Moves the package metadata from
setup.pyto[project]inpyproject.toml. The minimum setuptools is now 61, the first version that supports[project].setup.pykeeps only the extension modules andbuild_ext. It reads the version frompyproject.tomlwithtomllib(Python 3.11+) to pass it to the C++VERSION_INFOmacro.A pyproject-only config is not possible yet: pybind11 has no setuptools plugin, and setuptools'
ext-modulestable makes plainExtensions, which do not get the pybind11 include path or C++ standard flags.