Project Talk:Python/PYTHON TARGETS

use_python & system solvency
these should be noted in this wiki page.

USE_PYTHON='2.7 3.2 3.3'

666threesixes666 (talk) 17:30, 6 February 2014 (UTC)


 * As of late Portage automatically can handle Python switching interpreters, so this discussion can be closed. --Maffblaster (talk) 18:00, 23 August 2016 (UTC)

Per-package python targets
Shouldn't per-package python targets be mentioned on this page? I mean adding lines like this:


 * Yes please; I just spent 15 minutes figuring this out, dug up my password to add this information, found that I don't have permissions to edit the page, came here to suggest this, and here is the solution to this problem. This could be made more efficient.    AstroFloyd (talk) 08:35, 14 January 2017 (UTC)


 * I've added a few examples now. Michał Górny (talk) 21:27, 21 April 2017 (UTC)

Cleaning up unused python cruft?
I am still muddling through various ways to minimize "versions" of python packages (less bloat, faster re-emerge)...

There are certain packages (app-text/asciidoc comes to mind) that are stuck to 2.7 - OK. But how can I get a definitive list of what supports _only_ 2.7?

Other packages evolve and with each version they support newer python (e.g. dev-python/awscli)...

So, at the moment I somehow (=large hand-edited package.use) manage to "only" have python-{2.7,3.4,3.6} installed, although ideally I'd like to get rid of 3.4 if possible, along with disabling 3.4 in libraries that don't require it.

Many attempts at "playing with package.use"; "emerge -p"; "eix"; "equery" and back seem to just eat time...

Some examples of command-fu as to how to more effectively manage PYTHON_TARGETS per package would be great!

Easy fix
should be replaced with. Fturco (talk) 10:21, 5 January 2020 (UTC)