fix(build): migrate from setup.py to pyproject.toml #271
Conversation
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
This commit modifies the project so that its metadata is configured in the pyproject.toml file instead of setup.py. Signed-off-by: Phil Adams <[email protected]>
padamstx
force-pushed
the
toml-packaging
branch
from
ca445df to
71eb98b
Compare
ibm-devx-sdk
pushed a commit
that referenced
this pull request
Aug 8, 2024
## [0.55.3](v0.55.2...v0.55.3) (2024-08-08) ### Bug Fixes * **build:** migrate from setup.py to pyproject.toml ([#271](#271)) ([be63d03](be63d03))
|
🎉 This PR is included in version 0.55.3 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
PR summary
This commit modifies the project so that its metadata is configured in the pyproject.toml file instead of setup.py.
PR Checklist
Please make sure that your PR fulfills the following requirements:
Current vs new behavior
Does this PR introduce a breaking change?
Other information