Project Talk:Python/PYTHON TARGETS

Note
Before creating a discussion or leaving a comment, please read about using talk pages. To create a new discussion, click here. Comments on an existing discussion should be signed using ~~~~:

A comment [[User:Larry|Larry]] 13:52, 13 May 2024 (UTC)
: A reply [[User:Sally|Sally]] 03:55, 26 January 2025 (UTC)
:: Your reply ~~~~

Navigate to first

Open discussion
Good first discussion
Discussion needing discussion
Discussion needing help
Solved discussion

use_python & system solvency

Talk status

This discussion is done.

these should be noted in this wiki page.

root #python-updater

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

Talk status

This discussion is done.

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

FILE /etc/portage/package.use

category/package python_targets_python3_5

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?

Talk status

This discussion is still ongoing.

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! — The preceding unsigned comment was added by Thinrope (talk • contribs)

Easy fix

Talk status

This discussion is done.

/21etc/portage/package.use should be replaced with /etc/portage/package.use. Fturco (talk) 10:21, 5 January 2020 (UTC)