>I imagine this works for you only because you've upgraded from before
Fedora 38. The python community is moving to a model where you are barred
from installing non-distro packages into the regular namespace, and thus
pipx (or venv) is required. Here are the details:

Not quite.
The pip command (at least the fedora version) now will automatically
install packages inside the user space, specifically under
~/.local/lib/pythonX.XX/site-packatges/ and the executables under
~/.local/bin unless it is being run as the root user.  This does not
require using a venv to function, but does only operate as the user similar
to a venv.

I install system packages as the root user, but packages such as chirp (and
others) using pip as my regular user to avoid overwriting system packages
when version dependencies may differ.

Yes, this is a change from earlier designs but avoids the necessity of a
venv while still having what seems the same advantages.
I have not needed a venv to install anything for quite some time, even on
my RPi which runs ubuntu and uses octoprint which originally  did require
the venv.

I believe that for other distros pipx may perform similarly.

Jeff
KI7GJG



On Tue, Jun 4, 2024 at 3:12 PM Dan Smith via Users <
[email protected]> wrote:

> > Note that I do not use pipx.
> > I do my updates with pip using the command
> > `pip install --upgrade chirp-20240504.tar.gz`
> > and it does the install/upgrade flawlessly
> > This is on Fedora 40 and it has worked this way since Fedora 37 for me
> > with upgrades to each version in between (both of the OS and chirp).
>
> I imagine this works for you only because you've upgraded from before
> Fedora 38. The python community is moving to a model where you are barred
> from installing non-distro packages into the regular namespace, and thus
> pipx (or venv) is required. Here are the details:
>
>
> https://packaging.python.org/en/latest/specifications/externally-managed-environments/
>
> All new installs of every distro I've seen now have the flag enabled,
> which means pip refuses to do anything unless it's inside a venv. Fedora
> rolled this in 38, AFAIK. It's a major hassle for users, IMHO, and it seems
> a really unfortunate change to me. But, it's something upstream python and
> the distros have decided for us, so we just have to deal with it.
>
> --Dan
> _______________________________________________
> Users mailing list
> [email protected]
> https://lists.chirpmyradio.com/postorius/lists/users.lists.chirpmyradio.com
> To unsubscribe, send an email to [email protected]
> To report this email as off-topic, please email
> [email protected]
> List archives:
> https://lists.chirpmyradio.com/hyperkitty/list/[email protected]/
>
_______________________________________________
Users mailing list
[email protected]
https://lists.chirpmyradio.com/postorius/lists/users.lists.chirpmyradio.com
To unsubscribe, send an email to [email protected]
To report this email as off-topic, please email 
[email protected]
List archives: 
https://lists.chirpmyradio.com/hyperkitty/list/[email protected]/

Reply via email to