Veek M
Disciple
https://realpython.com/pipenv-guide/ So I was reading about pipenv and he says that
Now you make your changes to the code and run some tests to verify everything is still working as expected. (You do have unit tests, right?) Now, just as before, you lock your environment with pipenv lock, and an updated Pipfile.lock will be generated with the new version of the dependency. Just as before, you can replicate this new environment in production with the lock file.
When you pipenv install it will get the latest version for your python-app. Why do I need to Lock the install/environment? Usually lockfiles is used to resolve contention issues.. and why is the new version IN THE .lock? Usually .lock is empty..
Now you make your changes to the code and run some tests to verify everything is still working as expected. (You do have unit tests, right?) Now, just as before, you lock your environment with pipenv lock, and an updated Pipfile.lock will be generated with the new version of the dependency. Just as before, you can replicate this new environment in production with the lock file.
When you pipenv install it will get the latest version for your python-app. Why do I need to Lock the install/environment? Usually lockfiles is used to resolve contention issues.. and why is the new version IN THE .lock? Usually .lock is empty..