On Mar 12, 2015 4:25 AM, "Antoine Pitrou" <solipsis@pitrou.net> wrote:
>
> On Wed, 11 Mar 2015 13:43:25 -0600
> Neil Schemenauer <nas-python@arctrix.com>
> wrote:
> > This has been brought up elsewhere, I think this is a better forum
> > to discuss it. Changing /usr/bin/python directly to python3.x is
> > bad idea, in my option. It's going to cause users trouble and the
> > benefit to Python 3.x users is not worth it. Instead, let's try to
> > find a smooth migration path.
>
> As a data point, when you install Python 3 using Conda, the executable
> is already called "python":
>
> $ python

Brew and pyenv also rely upon $PATH to determine which executable named 'python[maj.min]' to run a script marked as executable with.

+1 for the /usr/bin/env python[maj[.min]] approach is likely most portable (because it uses $PATH for what it is for)

* OSX 10.9 is still on 2.7.5 (i think w/o SSL security updates(!))
* OSX 10.10 has ?.? ([1] lists 2.7.1 as most recent)
* I think it would be reasonable to request an update that adds a '/usr/bin/python2' symlink, so that paths can be '/usr/bin/env python[maj[.min]'.