[Python-Dev] Another update for PEP 394 -- The "python" Command on Unix-Like Systems

Antoine Pitrou solipsis at pitrou.net
Thu Feb 14 03:44:17 EST 2019

On Thu, 14 Feb 2019 00:57:36 -0500
Jason Swails <jason.swails at gmail.com> wrote:
> I literally just ran into this problem now.  Part of a software suite I've
> written uses Python to fetch updates during the installation process.  Due
> to the target audience, it needs to access the system Python (only), and
> support systems as old as RHEL 5 (Python 2.4 and later, including Python
> 3.x in the same code base, using nothing but the stdlib).  The shebang line
> was "#!/usr/bin/env python"
> It's been working for years, but was only now reported broken by a user
> that upgraded their Ubuntu distribution and suddenly had no "python"
> executable anywhere.  But they had python3.
> I suspect suddenly not having any "python" executable in a Linux system
> will screw up a lot more people than just me.  The workaround was ugly.

I'm not sure what you mean.  Isn't the workaround to install Python 2
in this case?



More information about the Python-Dev mailing list