Use flit-core<3.9,>=3.4 as the build backend #340
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
BeautyyuYanli
requested review from
wey-gu,
HarrisChu and
Nicole00
and removed request for
wey-gu and
HarrisChu
|
For now(with httpx dependency, to support centOS7 py3.6 build from source), this is the best way, but let's hold this change(not merge) until we have some time to verify the full nebula-ent build(need to not remove pyproject.toml in makefile) |
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.
Use flit-core<3.9,>=3.4 as the build backend, so that PEP517 and PEP621 can be available on Python >= 3.6
That means:
pip install .is available in Python 3.6pdm buildis available in Python 3.6pyproject.tomlis available on Python 3.6