Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#61137 - Pacman feature - Python pip wrapper

Attached to Project: Community Packages
Opened by Anel (anelge) - Thursday, 20 December 2018, 11:17 GMT
Last edited by Allan McRae (Allan) - Thursday, 20 December 2018, 12:50 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Motivation:
Today we have some conflict problems and we have both ways to install python packages are PIP and Pacman. Time to time it will produce new conflicts and we can't install new pip or pacman packages because the files already exists.

Description:
We could use prefixes for packages to indicate a pip package, for example:
sudo pacman -S python3 python2 p:pyshark p2:pyshark p:tensorflow. It will allow to install packages directly, use them inside of PKGBUILD and remove python-* and python2-* packages from the repository.

This task depends upon

Closed by  Allan McRae (Allan)
Thursday, 20 December 2018, 12:50 GMT
Reason for closing:  Won't implement
Comment by Levente Polyak (anthraxx) - Thursday, 20 December 2018, 11:40 GMT
do NOT ever under any circumstances install packages into your system folder using pip.

PS: this feature wont happen

Loading...