Adjust Dockerfile to new version of pipenv #487
Conversation
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
… create requirements.txt file
reihl
force-pushed
the
fix_dockerfile_pipenv
branch
from
36cb9da to
71f707d
Compare
Member
|
@nirs Hi Nir, |
Member
|
Getting rid of pipenv is better, but if this works it is an easier change. This project does not need pipenv locking. pip install with requirements.txt file is better and much faster. |
Member
|
Hi guys, we have a container friendly version in, no pipenv is used: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
pipenv has been change and now you need to use pipenv requirements to create requirements.txt file