Summary: | dev-lang/python-exec: prefers python2.7 when eselected python3 is unsupported | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Maxim Koltsov (RETIRED) <maksbotan> |
Component: | [OLD] Unspecified | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Maxim Koltsov (RETIRED)
2016-01-27 15:29:48 UTC
You're reporting the wrong bug! As I already told you, it's 'eselect python show --python2' causing this ;-P. Now, for some background. It was done like this to cover the following scenario: a user has python2.7 eselected but runs py3-only app. In this case, the default order would prefer newest py3 version while an older one could be selected (with --python3). So it also does the opposite: if user has python3 eselected, and matching py3 version is not supported, it falls back to eselect python2. Since that's eselected at least. The question is: do we want to change that logic, and how? We could implement a custom preference list. But should we integrate that with eselect-python? Should we make that override py2/py3 selections? The current live ebuilds fix that. Please give them some more testing before I do a release. (python-exec + eselect-python) And now python-exec-2.4 is out (p.masked), with new totally awesome /etc/python-exec/<script-name>.conf config overrides! Fixed in ~arch. |