Re: Python 3 binaries

[Andreas Enge]

On Sun, Sep 01, 2013 at 10:20:18AM +0200, Brandon Invergo wrote:
> Here's what it looks like on my Parabola system, which I think is a sane
> way of doing it (ok, there's no *truly* sane way of doing it):
> $ ls -l /usr/bin/python*
> lrwxrwxrwx 1 root root  1K May 21 17:50 /usr/bin/python -> python3
> lrwxrwxrwx 1 root root  1K May 21 17:50 /usr/bin/python-config -> 
> python3-config
> lrwxrwxrwx 1 root root  1K May 12 18:01 /usr/bin/python2 -> python2.7
> lrwxrwxrwx 1 root root  1K May 12 18:01 /usr/bin/python2-config -> 
> python2.7-config
> -rwxr-xr-x 1 root root  7K May 12 18:01 /usr/bin/python2.7
> -rwxr-xr-x 1 root root  2K May 12 18:01 /usr/bin/python2.7-config
> lrwxrwxrwx 1 root root  1K May 21 17:50 /usr/bin/python3 -> python3.3
> lrwxrwxrwx 1 root root  1K May 21 17:50 /usr/bin/python3-config -> 
> python3.3-config
> -rwxr-xr-x 2 root root 11K May 21 17:50 /usr/bin/python3.3
> lrwxrwxrwx 1 root root  1K May 21 17:50 /usr/bin/python3.3-config -> 
> python3.3m-config
> -rwxr-xr-x 2 root root 11K May 21 17:50 /usr/bin/python3.3m
> -rwxr-xr-x 1 root root  2K May 21 17:50 /usr/bin/python3.3m-config

This is more or less what happens now, with the default implicitly being
Python 2, since the Python 2 package ships a binary "python" and the Python 3
package ships a binary "python3". Since we promise to follow upstream as
closely as possible, it would make sense for us to keep this situation.

> Shebangs are routinely changed in Parabola to accommodate this but since
> shebangs are also routinely being changed in Guix anyway, this shouldn't
> be a problem. 

This is what my patch that I sent previously to the list should accomplish.

Thanks for the input!

Andreas