Refactor pipenv usage according to semi-official best practices. #144
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
timofurrer
force-pushed
the
feature/cleanup-pipenv-use
branch
from
b7d9ac8
to
ca076ff
Compare
|
I am almost complete with my own "best practices" resolving usage of
|
|
Thanks for the write-up. I hope that will lead to a sane best practice guide. I'll definitely follow it there. |
|
I'll merge this for now so we don't miss anything in |
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.
@kennethreitz Can you shed some light into this. If this is really how pipenv should be used in our case?
Closes #142