Drop setuptools, use flit #519
Open
+120
−146
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
… requirements_upstream.txt to CI, adjust configurations
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.
Pull Request Checklist:
number) and pull request (:pull:number) has been added.What kind of change does this PR introduce?
setuptoolsbuild backend forflit.requirements_upstream.txtfile to CI folder.Manifest.in.Does this PR introduce a breaking change?
Yes.
setuptoolsis no longer used to build the package. Build requirements are much simpler.Other information:
flitis the backend used by the cookiecutter and most Ouranos projects. It is much simpler in its configuration and design. We don't compilexscennor do we manage dependencies using lock files (likepoetrydoes).