Repository navigation
WiP: Added PEP518 support - #1007
Closed
carstencodes wants to merge 1 commit into
Closed
carstencodes wants to merge 1 commit into
carstencodes wants to merge 1 commit into
Conversation
The PIP518 support as described in PyCQA#813 has been implemented roughly. It uses the toml package, since the toml package describes itself as being Python 2 compatible. Using another package will create a dependency that might not be wanted. Hence the dependency is treated optional as an extra, so consumers can decide which revision they would like to use. TODO: Unit test must be written explicitely.
7 of 9 tasks
|
Any update when this will be fixed? |
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
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.
The PIP518 support as described in
#813
has been implemented roughly.
It uses the toml package, since the toml package describes itself as
being Python 2 compatible.
Using another package will create a dependency that
might not be wanted. Hence the dependency is
treated optional as an extra, so consumers can decide
which revision they would like to use.
TODO: Unit test must be written explicitely.