On Mar 12, 2015 5:00 PM, "Andrew Barnert"
On Mar 12, 2015, at 6:55 AM, Wes Turner
wrote: On Mar 12, 2015 4:25 AM, "Antoine Pitrou"
wrote: On Wed, 11 Mar 2015 13:43:25 -0600 Neil Schemenauer
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
+1 for the /usr/bin/env python[maj[.min]] approach is likely most
* 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]' to run a script marked as executable with. portable (because it uses $PATH for what it is for) python[maj[.min]'.
http://openradar.appspot.com/radar?id=5833516721897472
If you want to file your own bug report with Apple, you can mention that
it's a dup of radar 20143311. I sent an email to product-security AT apple.com ( https://www.apple.com/support/security/) with a link to this thread; because TLS.