On 14 April 2015 at 16:38, Scott Kitterman <deb...@kitterman.com> wrote: > On Monday, April 13, 2015 10:36:43 PM Barry Warsaw wrote: >> On Apr 14, 2015, at 01:57 AM, Matthias Klose wrote: >> >#! /bin/sh >> >python=$(shuffle /usr/bin/python2 /usr/bin/python3) >> >exec $python "$@" >> >> That was more or less the joke I made at the Pycon Language Summit. It's >> too twisted *not* to implement. :) >> >> But the idea of a (perhaps less perverse) launcher would solve the PEP 394 >> dilemma of what /usr/bin/python should point to when there's no Python 2 on >> the system by default. E.g. maybe it reads a configuration file to >> determine whether it runs /usr/bin/python2 or /usr/bin/python3. > > Even after Python (meaning python2.7) is no longer in the archive (let alone > part of some type of default install), people might still roll their own. I > think the only possible answer to the question of what should /usr/bin/python > point to when there's no python2 on the system is that it shouldn't exist. > > If you want python (which include /usr/bin/python), install it. If you want > python3, then the interpreter you're looking for is found at /usr/bin/python3. > > There's no dilemma to solve.
I agree. Maybe in 2029 we can revisit it, but I've seen absolutely no good reason to push on this other than 'Gentoo did it' - scratch that, absolutely no good reason to push on it. -Rob -- Robert Collins <rbtcoll...@hp.com> Distinguished Technologist HP Converged Cloud -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAJ3HoZ0BPr=fbnmqrwc5mz_bcj-bua4+qlu+a64c-vjzn7o...@mail.gmail.com
