On Fri, Dec 9, 2022 at 5:04 PM Audrey Toskin <terrycloth@xxxxxxxxxxxxxxxxx> wrote: > > DNF modules let you install multiple different versions of Python 3, and the `alternatives` tool lets you change which is the default version invoked by `/usr/bin/python3`. > > However, at least for *Enterprise Linux 8, it seems a lot of packages were built assuming the distro's default Python 3.6, but at runtime only invoke "Python 3", not 3.6 specifically. It seems that I still need Python 3.6 for most packages installed via DNF on EL8, but I also definitely need Python 3.8+ for multiple packages I use installed with PIP. So, the workaround to having both installed on my system at the same time would be to edit the shebangs to include the minor version of Python that each application requires. > > ...Right? I wanted a sanity check before I bother sending spam to EPEL package maintainers. Or, is this even a reasonable thing to ask package maintainers to change, or should I just start patching the local shebangs myself? Or is there a better solution? RHEL 8 has brp-mangle-shebangs, and when correctly invoked (which EPEL should do already), the interpreter path is already rewritten for you. My packages in EPEL 8 seem to have this, at least. -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
