I've installed two Pythons (~amd64) and 2.6 eselected: % eselect python list Available python interpreters: [1] python2.6 * [2] python3.1 I expect bpython to be installed for both of them, and working with eselected version. But `/usr/bin/bpython` begins with #!/usr/bin/python3.1, so bpython a) can't work with python 2.6; b) may not work at all, since pygments may not be installed as a 3.1 package.
/usr/bin/bpython is now renamed to /usr/bin/bpython-${Python_slot}.
Excuse me, but what's the point? Now we have two _identical_ files: % diff /usr/bin/bpython-2.6 /usr/bin/bpython-3.1 1c1 < #!/usr/bin/python2.6 --- > #!/usr/bin/python3.1 Why not just be happy with '#!/usr/bin/python' interpreter like with most Python scripts? Or, alternatively, symlink /usr/bin/python to /usr/bin/bpython-${eselected_Python}, like it's done with Python itself.
distutils_src_install() now renames Python scripts and generates appropriate wrapper scripts.