[Baypiggies] Whither `python` OR `python2` and `python3`?

[wesley chun]

Thanks for all the commentary. It's good to see what people are thinking.
It turns out my problem wasn't related to the original "cause" that I
thought. It was the Buildpacks system (how I build containers while
avoiding Docker) that I was using to create the container had
/usr/bin/python as a symlink to... python (not python2 nor python3),
meaning a circular self-referencing... reference. I got the responsible
team to fix that bug so that "python" links to whichever version of Python
is default in that container image, and everything works again.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
"A computer never does what you want... only what you tell it."
    wesley chun :: @wescpy <http://twitter.com/wescpy> :: Software
Architect & Engineer
    Developer Advocate at Google
<https://cloud.google.com/developers/advocates/wesley-chun/> by day; at
night: Core Python <http://amzn.com/dp/0132269937>



On Fri, Oct 7, 2022 at 3:06 PM James Salsman <jsalsman at gmail.com> wrote:

> >... I very much want /usr/bin/python working for python 2 scripts and
> crashing on python 3 scripts in order to avoid silent bugs due to running
> the wrong interpreter.
>
> I agree strongly. Does anyone know if this is just Ubuntu or is Debian
> doing this too?
> _______________________________________________
> Baypiggies mailing list
> Baypiggies at python.org
> To change your subscription options or unsubscribe:
> https://mail.python.org/mailman/listinfo/baypiggies
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/baypiggies/attachments/20221103/2ede047c/attachment.html>