Re: Pip installs to unexpected place

On Fri, 18 Apr 2025 at 16:50, Peter J. Holzer via Python-list
<python-list@python.org> wrote:

>
On 2025-04-18 13:24:28 +1200, Greg Ewing via Python-list wrote:

On 18/04/25 9:41 am, Mats Wichmann wrote:

There's just not a really great answer to this.

>
Seems to me a system-installed application shouldn't be looking in the
user's .local packages in the first place. That should only be for things
the user has installed "for this user".

>
It's not the application that looks into .local, it's Python. If you say
that a system-installed Python shouldn't look into ~/.local, then you've
just disabled that mechanism completely. If not then Python would
somehow have to distinguish between system-installed and user-installed
scripts. This isn't as easy as checking whether the path starts with
/usr/bin or whether it belongs to root. Tying into the system's package
manager doesn't look appealing to me (not to mention that it might be
unacceptably slow).

Couldn't the system-installed scripts have a shebang like:

#!/usr/bin/python3 -s

--
Oscar