Skimming the comments in this thread I see firstly a lot of hate towards pipenv that I don't understand. I mean on a technical level, I don't understand what yo

Skimming the comments in this thread I see firstly a lot of hate towards pipenv that I don't understand. I mean on a technical level, I don't understand what you're talking about. Secondly, interspersed beteween the hate I could count at least 6 alternatives to pipenv. So as a python user I don't know who to trust. I stumbled across pipenv at a time when I was managing a "global" directory of virtualenvs instead of putting them inside each project dir. So I could do source ~/.venvs/project/bin/activate because I was tired of having different .venvs inside project dirs. Pipenv seemed like a welcome change and I especially liked doing pipenv run commands. I still run my dev servers with pipenv run. Keeps my environment clean. Sourcing a virtualenv before would lock that shell to only working with one project, one environment. I have noted some issues with pipenv, the first was in ansible deployment but it wasn't a show stopper. The second issue I can't remember so it must have been fleeting. As someone else pointed out, maybe it's for simple users like me who don't need to understand the advanced internals of Python. Edit: Right! The 2nd issue was actually that I work with some services that are spread across three different git repos/projects. Maintaining a central virtualenv for multiple projects needed figuring out but I think I've resolved it by having a parent dir for the service where the virtualenv is created and then pipenv commands in the sub-dirs (git repos) use the parent virtualenv. I've also noted some confusion in pipenv on whether it's using python3 or 2. A pipenv --two project might try to install packages using pip3 for some reason. Lastly, a lot of the hate towards pipenv seems to be directed towards how it was launched and marketed. Which in my opinion has little to do with the tool and how it might help users with Python. Open source has always been and will always be a wild ecosystem where the best tool floats to the top by word of mouth alone. So why be mad because someone used python.org to promote a tool when you can contribute your time and knowledge to promoting your favorite yourself. I just don't like when there are too many options to choose from and I don't know which one is right for me. I guess time will tell. Also I don't really do CI/CD pipelines yet so maybe a lot of issues are unknown to me.