You are not logged in.
Pages: 1
I find pacman and pip very inconvenient to manage python packages.
Sometimes, I want to install a python package and use pip, and then I want to install another (non-python) package with pacman which depends on the previous python package. The result is the installation will fail because python package files already exist and I have to uninstall python package with pip and install the package with pacman.
Now, I always use pacman to search whether there is already a python package in arch repo before I try pip. However, some packages in AUR requires python packages in AUR as well. I can choose to install package from AUR but I am not willing to do so because some python packages are unmaintained.
So, It seems pacman and pip are not working well with each other. Is there a solution and do developers have a plan to make pacman to work well along with other package managers?
Last edited by wangchong (2015-08-20 01:51:26)
Offline
You can create and maintain PKGBUILDs for the packages you use.
Offline
You can create and maintain PKGBUILDs for the packages you use.
Of course, but this practice doesn't seem to be smart and consistent. What if I don't know how to package and just want to use Arch linux?
Offline
Offline
There is a nice tool called pipman in the AUR which helps you with creating arch packages from python packages. Still, you have to know how packages are defined and created.
https://aur.archlinux.org/packages/pipman-git/
Edit: By the way, the arch package format is stupidly simple, so if you are able to use arch you should be able to create packages after a short learning period.
By the way, if I want to manage packages with pip for a new project, I mostly create a new venv for that project. Sometimes I also use the venv I created as a catchall pip environment.
Last edited by progandy (2015-08-20 02:06:04)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' | alias ENGLISH='LANG=C.UTF-8 ' |
Offline
Pages: 1