Hacker News Reader

So this is sort of like a virtualenv, except you don't need to activate anything, it just looks within the main project folder for a __pypackages__ folder, and uses that to look for packages

I use pipenv

Pipenv is only focused on solving one problem, deploying complete packages you wrote to a server you have complete control over. It doesn't really care about the problem of developing applications and libraries for distribution and installation by third parties and on platforms running different python version/OS etc. than what it was developed on.

I use only virtualenv and have never really had any issues with it for separating out my project environments.

Perhaps this is more of an issue with larger projects, but I also noticed that 'no need to use virtualenv' as a positive.

You kind of answered your own question. Virtualenv alone is too much work so you're using a tool like pipenv to streamline it. This is a similar idea to have less ritual and a faster developer workflow.

It's a single command more, and then you don't need to prefix everything with pipenv run.

> I use pipenv

> When deploying to kubernetes it works the same way

Can you elaborate on this?