public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Kenworthy <bill@kenworthy.id.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] python breakage
Date: Sun, 3 Nov 2024 13:33:02 +0800	[thread overview]
Message-ID: <0c8c5852-be7f-4a6a-815f-c082c133e72b@kenworthy.id.au> (raw)
In-Reply-To: <c587ea46-e061-42b5-9c39-3fbcec1f9958@gentoo.org>


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


      reply	other threads:[~2024-11-03  5:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-02  0:51 [gentoo-user] python breakage William Kenworthy
2024-11-02  2:04 ` Matt Jolly
2024-11-03  5:33   ` William Kenworthy [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0c8c5852-be7f-4a6a-815f-c082c133e72b@kenworthy.id.au \
    --to=bill@kenworthy.id.au \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox