From wescpy at gmail.com Thu Nov 3 02:52:50 2022 From: wescpy at gmail.com (wesley chun) Date: Thu, 03 Nov 2022 06:52:50 -0000 Subject: [Baypiggies] Whither `python` OR `python2` and `python3`? In-Reply-To: References: <14fe5f46ff557e6816d71f5acf98608649efaafd.camel@dancingmushrooms.com> Message-ID: 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 :: Software Architect & Engineer Developer Advocate at Google by day; at night: Core Python On Fri, Oct 7, 2022 at 3:06 PM James Salsman 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: