When comparing pipenv vs Conda, the Slant community recommends Conda for most people. In the question“What are the best Python package managers?” Conda is ranked 1st while pipenv is ranked 2nd. The most important reason people chose Conda is:
They are fast and reliable as they do not need to compile before installation.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Easy to work with different Python versions in virtual envs
In pipenv, spinning up an virtual environment for Python 2 or 3 is simply just pipenv --two
or pipenv --three
.
Pro Similar to pip
If you already know pip, you know most of pipenv too
Pro PyCharm integration
PyCharm directly integrates with pipenv.
Pro Has a dependency graph
Running pipenv graph
gives you a nice overview of what your dependencies are.
Pro Binary installs
They are fast and reliable as they do not need to compile before installation.
Pro Allows for multiple environments
It is great for developers since you can easily switch between complete environments with different versions of packages, for testing and development.
Pro Open source
Conda is open source and on Github, so if you see something wrong you can fix it and submit a patch.
Cons
Con Buggy
Con Doesn't use modern Python package management standards
Con A bit slow due to the dependency checks (lock)
It’s obviously an added feature compared to pip, but it does get significantly slower with a project with lots of packages.
Con Doesn't have everything
Conda is relatively new and has a smaller user-base, so the set of packages available is limited.
Con No way to resume downloads
Any download that is canceled or interrupted will have to be started over from the beginning as there is no built in solution for resuming downloads.