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".
--
Greg
--
https
On 4/17/25 15:15, Grant Edwards via Python-list wrote:
On 2025-04-17, Left Right via Python-list wrote:
Also... when installing stuff with pip --user, it is always a package
that is not installed for the system (usually not even available for
the system). How can that "break system packages"?
On 2025-04-17, Left Right via Python-list wrote:
>> Also... when installing stuff with pip --user, it is always a package
>> that is not installed for the system (usually not even available for
>> the system). How can that "break system packages"?
>
> pip installs dependencies. Dependencies may di
> Also... when installing stuff with pip --user, it is always a package
> that is not installed for the system (usually not even available for
> the system). How can that "break system packages"?
pip installs dependencies. Dependencies may disagree on the version
with the system packages.
This is
On 4/17/2025 4:58 AM, Roel Schroeven via Python-list wrote:
Op 15/04/2025 om 20:31 schreef Mats Wichmann via Python-list:
To be clear: you do not have to activate a virtualenv to use *Python*
from it. If you just call the python by the path it's in, it figures
everything out (and sets some vari
Op 15/04/2025 om 20:31 schreef Mats Wichmann via Python-list:
To be clear: you do not have to activate a virtualenv to use *Python*
from it. If you just call the python by the path it's in, it figures
everything out (and sets some variables you can query vi sysconfig if
you have reason to actua
