On Apr 21, 2015, at 10:42 AM, Geoffrey Thomas wrote: >For third parties who want to distribute scripts that run out-of-the-box >everywhere (installers, cross-platform system management or monitoring >scripts, build scripts, etc.), Python 3 isn't an option. If we remove Python >2 from the default install in Debian, Python 2 ceases to be an option too. So >they'll start using sh or perl or something, or ship compiled code, both of >which I think are net negative options.
Do you think that will happen even if Python 2 is just an apt-get away? >One other point that I glossed over: the interactive command "python" >currently runs either Python 2 or nothing. Would we like it to run Python 3 >at some point? If end users do this on their own via a symlink (which is very >tempting) they'll get mysterious failures from certain third-party >applications. That's the $64,000 question. :) >A simpler version of the proposal is that interactive use (no arguments, and >isatty(0)) always launches the latest Python interpreter of any major >version, but all other use always launches the latest Python 2 interpreter, >or prints an error message. Careful about `python -i`; that's essentially interactive use too. Cheers, -Barry -- 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/20150421111548.71594...@limelight.wooz.org