On 2/11/24 10:04, Matt Jolly wrote:
Hi Bill,
On 2/11/24 10:51, William Kenworthy wrote:
My questions (for gentoo) is this another gentoo only hack, or an
upstream hard requirement and how can it be turned off.
BillK
This is PEP 668 in action.
https://peps.python.org/pep-0668/
https://packaging.python.org/en/latest/specifications/externally-managed-environments/#externally-managed-environments
While annoying the intent here is to stop users from shooting
themselves in the foot by breaking critical system packages.
As you've identified, virtual environments are the "solution"
to this "problem".
https://packaging.python.org/en/latest/specifications/virtual-environments/#virtual-environments
If you wish to go back to the old behaviour you can install mask
the EXTERNALLY_MANAGED file.
Cheers,
Matt
Hi Matt, as per my previous email I already know about
"EXTERNALLY_MANAGED" - this is really independent of the the problem
PEP668 addresses which is package managers. What I have run into (see
the error message I included with the previous email) is that after
deleting the "EXTERNALLY_MANAGED" tokens something is now enforcing
using a venv but isnt providing a workaround for older packages and
those that dont use a venv. I am not sure if its within python or
gentoo so I am asking for a hint as its a lot of code to go through.
Nothing is showing up that I have found in searching so far as
everything is assuming its a user doing a direct install, not a python
module auto installing/updating missing deps on startup.
BillK
It isnt clear that is being caused by the
