4 ms·
pip is a neat system and all, but I still don't see why to use that versus a system package?
by e1ven 15y ago
pip is a neat system and all, but I still don't see why to use that versus a system package?
- freyrs3 15y agoSystem packages install globally, pip can install globally or inside a virtualenv.
- timtadh 15y agoUpdating the source package is easier for one. Ubuntu's packages are often out of date, especially if you are running an LTS. It also integrates nicely with virtualenv which makes managing dependencies easier, via pip freeze.
- politai 15y agoSystem package's availability vary a lot with the distribution you're using. For instance I use Debian and my web hosting provider is based on CentOS and share my REQUIREMENTS.txt file.I can't really depend on the packages being available on every distro's repository, let alone the same version. Also, I wouldn't like to install some packages system-wide (a friend's personal project from a github repository) so I use pip and virtualenv in a similar manner as the article recommends to maintain a per project dependency library. That's how I see it :)
- c4urself 15y agoif you have multiple projects on a system you may have different dependency requirements. module with version 1 for one project and the same module with version 2 for the other project.
- d0mine 15y agopkg_resources.require() can handle this case. Though `virtualenv` is more explicit.
- mark_story 15y agoSystem packages are going to miss some package that exists in pypi. Using pip is also good if your company maintains their own internal toolsets, and want to be able to easily reuse those across multiple applications.
- brndnhy 15y agovirtualenv can't isolate your system's package util like it can isolate pip.