Arch Linux

Kotrfa

Member

Registered: 2012-10-25

Posts: 213

Python - pip or AUR

Hello,

are there any (dis)advantages of using pip instead of installing packages from AUR (when they have good mantainer)? Currently I mix it on system level, what I guess isn't good idea... And pip should be "officialy included" in python 3.4, which will be out soon.

Thank you

Pajaro

Member

Registered: 2004-04-21

Posts: 884

Re: Python - pip or AUR

using pip you add files to your system which are not handled by pacman. use what suits you best.

firecat53

Member

From: Lake Stevens, WA, USA

Registered: 2007-05-14

Posts: 1,542

Website

Re: Python - pip or AUR

1. Using pip at a system level ('sudo pip install') you don't have any way of telling what packages were installed via pip vs via pacman/AUR.
2. pip can me more convenient sometimes for a quick one-off installation to test something...just try to remember to 'pip uninstall' when you're done so you don't get conflicts in the future. And it's cleaner
3. If you don't need a package systemwide, consider using 'pip install --user' or working inside a virtualenv.
4. I don't believe (not 100% sure without a quick search) there is a built-in pip equivalent to 'pacman -Syu' for a global package update (which can be simulated by some of the AUR package managers for AUR packages).

Scott

---

Github

x33a

Forum Fellow

Registered: 2009-08-15

Posts: 4,587

Re: Python - pip or AUR

I personally like to keep AUR packages to a minimum. So I prefer pip.

Kotrfa

Member

Registered: 2012-10-25

Posts: 213

Re: Python - pip or AUR

Wouldn't be a solution to:

1. Install packages from core repos by default to /usr/lib/something
2. Create virtualenv (now it is by default included with pip since python 3.3, python 3.4 respectively)
3. Install packages from pip (which are not in core repos) to this virtualenv
4. Add virtualenv to pythonpath

It could solve both problems:
1. You can distinguished which packages were installed by PIP and which by pacman. Simply just by looking what is in the directories, e.g /usr/lib/python3.4/site-packages and /opt/virtualenv/python3.4/site-packages
2. You could set "nice" permission to virtualenv, so you hadn't to use sudo with PIP (what is IMHO not a very clear - similiarly why we don't use sudo with make)

But I haven't tested. Maybe in the future. It will have to be a really nice day, so I won't smash my head against the wall.

Last edited by Kotrfa (2014-03-29 21:15:53)