In general, pip is dangerous and a mess to use. This is why people who rely only on pip MUST use virtualenv, but even then pip sometimes misbehaves and installs to the wrong places. On the other hand, pip can only install Python packages, and it quite often screws up the installations on multi-user systems, breaking global system dependencies and/or the user's dependency stacks. You do not need a third-party environment management system with conda. By default when you install conda for the first time, the default env is used (I think its called "base" or something like that), and will remain in use until you create & switch to another env. Also important to note that, as of the most recent versions of conda, conda's env is always active. In a lot of ways, conda serves as a lightweight userspace alternative to Docker for isolating software stacks. This is critical because it means that you can install complex software stacks on a system (such as your employer's heavily regulated production server) without needing root privileges. Also, conda is able to do all these software and package installations in an isolated, userspace manner. conda has an env system that allows you to have all of these installed across multiple different environments. You can install R, R libraries, Node.js, Java programs, C and C++ programs and libraries, Perl programs, the list is pretty long and limitless. You can install entire software stacks such as Python + Django + Celery + PostgreSQL + nginx. With conda you can install much more than just Python libraries.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |