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. Scott K -- 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/36643332.m5KcQVD1Ai@kitterma-e6430