On 10. 12. 22 17:53, Orion Poplawski wrote:
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.
Yeah, this should get done automatically, but on my syste
On Fri Dec 9, 2022 at 22:04 +, Audrey Toskin 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`.
This is not the case on any current Fedora release. AFAIK, only
On 12/10/22 06:38, Neal Gompa wrote:
On Fri, Dec 9, 2022 at 5:04 PM Audrey Toskin
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 *Enterp
On Fri, Dec 9, 2022 at 5:04 PM Audrey Toskin
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 o
I'm wondering how you specify Python 3.8+ in the shebang ...
If the EPEL 8 packages work with the EPEL 8 python then there is nothing to fix
on the packaging side, really. For pip installs virtualenv or conda and the
like seem to be the way forward, or adjusting their shebang to the non-default
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,
