use pyproject.toml for project metadata and flit_core as build backend
#154
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
davidism
force-pushed
the
release-0.16.0
branch
from
1bd5a5c
to
bc34964
Compare
davidism
force-pushed
the
release-0.16.0
branch
from
bc34964
to
6ca047c
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Use
pyproject.tomlinstead ofsetup.pyfor project metadata. Useflit_coreinstead ofsetuptoolsas the build backend. Remove old release scripts, as that is handled by the publish workflow now.This PR is also being used as the 0.16.0 release target for the new publish workflow. In the future, a specific PR for the release should be made.