Migrate to PEP-621 compliant pyproject.toml #94
Merged
Conversation
This file contains 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
rmarquis
force-pushed
the
pep621
branch
2 times, most recently
from
d6afdfc
to
94566b1
Compare
* Rename build.py to buildcpp.py so it does not interfer with `python -m build`, allowing the packaging to be done successfully.
|
Closed
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.
As poetry does not comply with the PEP-621 standard and won't for the foreseable future
(see python-poetry/poetry#3332 for details),
this migrates the pyproject.toml file from poetry specific syntax to a compliant version,
using the hatchling backend.