Recommend using pip for simple poetry projects #471
Merged
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.
Description:
This is a brief addition to the README that simplifies a common use-case: poetry projects that are simply installed via
poetry install
can usually be simplypip install
ed.Obviously, users that need to use, e.g.
poetry publish
can't take advantage of this.But most use cases are simply
poetry install
and then running everything in a virtualenv.If you are keeping your workflows simple, though, you already have isolation: the CI runner.
Does it really work? The build-system section will direct
pip
to loadpoetry_core
to perform the actual build. That was the point of PEP 517.And
poetry.lock
is fully specifiying everything that needs to be cached.Related issue:
#374 flags an incorrect python version being loaded. #369 questions why you need to install poetry. For those users that can do without the full
poetry
CLI, this solves those problems implicitly.Check list: