Python 2 and 3
Python#Python_3 doesn't mention http://python-future.org/ . It has been recently added to the repos: . I know nothing about python, so I just dropped a note here. -- Karol (talk) 10:54, 30 August 2015 (UTC)
- I know python well, but I don't know what's "python-future" xD We can add info about it if another users say it's a good idea -- Kycok (talk) 13:19, 30 August 2015 (UTC)
- To me it seems like a regular Python package (with rather self-assured name), providing tools similar to the older and limited 2to3 tool. It's not a new implementation or something like that, the future of Python is to switch to the 3 branch completely. I have no idea why they still (unofficially) backport everything to the 2 branch, thus delaying the inevitable. -- Lahwaacz (talk) 19:59, 30 August 2015 (UTC)
- That section is targeted at packagers, dealing mainly with the python -> python3 symlink. As far as I understand, the code has to be written explicitly for python-future (or converted automatically and checked) in order to use their features, it can't be used by packagers just for building the packages. -- Lahwaacz (talk) 20:23, 30 August 2015 (UTC)
Useful tip for package conflicts with pip?
I found a useful little one-liner that will give you all python packages installed site-wide that are not from a pacman package, and think it might be a useful thing to add?
pacman -Qo /usr/lib/python*/site-packages/* | grep 'No package owns'
- Using pip to install into
/usr/lib/is discouraged. There is Pacman/Tips_and_tricks#Identify_files_not_owned_by_any_package for general cleanup. -- Lahwaacz (talk) 14:32, 17 August 2016 (UTC)