Right now, when running python-exec wrapped script that does not have back-end matching currently eselected python version, it will choose another version by some internal logic. For example, I have eselected python3.5, then I try to run a script that supports only 2.7, 3.3 and 3.4. python-exec starts it using 2.7, while I'd like to start it with 3.4. I think it would be great if python-exec had some way of controlling python version preference.
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.
