Hey all, An "interesting" Linux support issue at work with another Linux distribution opened my eyes to the possibility of how badly things would break if /usr/bin/python3 was swapped or otherwise altered by an external force. In such a scenario where it was overridden to point to another Python 3 interpreter that wasn't the system one, things would break pretty badly.
Now that we've been moving toward a model where it becomes possible for first-party or third-party multi-Python RPMs, I'm wondering if it would make sense to evolve the shebang mangling for Python to resolve to the fully qualified Python interpreter path (that is, /usr/bin/pythonX.Y instead of /usr/bin/pythonX) for packaged Python code. Presumably this may make things easier for switching Python versions without everything breaking, too. In practice, I don't think this is a *huge* issue Fedora-side, since we don't manage /usr/bin/python3 via alternatives. But I can easily see people wanting /usr/bin/python3 to be swappable in Red Hat Enterprise Linux, while everything is still parallel installable and fully functional. The Python interpreter packaging even mostly supports this now. What do y'all think? Is this doable? Is this desirable? -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org
