Thanks for the tips, so many tools I didn't know about!
My turnoff with pipenv is that it requires the user to enter a "sub" shell or use "pyenv run" to load the environment instead of just loading it in the current shell (like virtualenv activate does). The idea of the lock file was truly needed in Python realm though
Thanks for the tips, so many tools I didn't know about!
My turnoff with pipenv is that it requires the user to enter a "sub" shell or use "pyenv run" to load the environment instead of just loading it in the current shell (like virtualenv activate does). The idea of the lock file was truly needed in Python realm though
pipenvis still evolving. Right now it has some issues with dependencies resolution on a big projects. And sub-shell bothers me too.But it already is so much better than
pip!ahha definitely! I wonder if "pipenv run" has any impacts in production. I've never deployed a project using pipenv. I'll have to study it a bit more.
Thanks!
Then take a look at our
djangotemplate: github.com/wemake-services/wemake-...It uses
pipenvfor production (alsodocker,gitlab ci, andcaddy). Works perfectly fine!Thanks Nikita, there's a lot of good stuff in there! :-)