3 ms·
People please stop engaging with pipenv and just use conda. Even critical arguments are mistakenly acting like pipenv deserves a seat at the table. Just don’t e
by mlthoughts2018 8y ago
People please stop engaging with pipenv and just use conda. Even critical arguments are mistakenly acting like pipenv deserves a seat at the table. Just don’t engage. It’s like the creationism of Python packaging.
- malcolmgreaves 8y agoI don't understand why this comment isn't higher! Honestly, using `conda` eliminates the pain of python dependency & environment management entirely. Clone a repo, do `conda env create` (from the project's `environment.yml`), then `source activate $ENV_NAME`. Straightforward. Easy. But most importantly, reliable!
- m_ke 8y agoIt's great but can be a pain if you develop on a mac and try to replicate your env on linux because the env files are not portable. The CLI can be confusing at times too, I always have to google how to create a new env or export it.
- mlthoughts2018 8y agoThe exact use case I use conda for at work is developing on Mac and automatically export the same env to various linux platforms. Why do you suggest conda doesn’twork for that? It’s one of the things conda specifically does. When recreating the same env on a different platform, it will resolve the dependencies for that platform, so there are no cross-platform issues of the underlying env unless the library being installed simply doesn’t support that platform, in which case _no_ environment manager could possibly solve that specific problem.