Reword cross-reference to the poetry project #508
Merged
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
The key design distinction between pipenv and poetry isn't the overall scope of the projects, but rather the assumptions we make about how projects are going to be structured. pipenv focuses mainly on "git push" and "git archive" style publication, where there's a private distribution pipeline between the repo and production systems (e.g. this is really common in SaaS and embedded systems). poetry, by contrast, focuses on the case where a pyproject.toml file is already present, at which point having Pipfile as well (as `pipenv` requires if you want to use it to manage development and testing environments) may feel redundant.
theacodes
approved these changes
May 23, 2018
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 key design distinction between pipenv and poetry isn't
the overall scope of the projects, but rather the assumptions
we make about how projects are going to be structured.
pipenv focuses mainly on "git push" and "git archive" style
publication, where there's a private distribution pipeline
between the repo and production systems (e.g. this is
really common in SaaS and embedded systems).
poetry, by contrast, focuses on the case where a pyproject.toml
file is already present, at which point having Pipfile as well (as
pipenvrequires if you want to use it to manage developmentand testing environments) may feel redundant.
Closes #506