[Python-Dev] Deprecate PEP 370 Per user site-packages directory? (original) (raw)
Paul Sokolovsky pmiscml at gmail.com
Sat Jan 13 14:34:00 EST 2018
- Previous message (by thread): [Python-Dev] Deprecate PEP 370 Per user site-packages directory?
- Next message (by thread): [Python-Dev] Deprecate PEP 370 Per user site-packages directory?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hello,
On Sat, 13 Jan 2018 19🔞41 +0100 Christian Heimes <christian at python.org> wrote:
[]
>> Nowadays Python has venv in the standard library. The user-specific >> site-packages directory is no longer that useful. I would even say >> it's causing more trouble than it's worth. For example it's common >> for system script to use "#!/usr/bin/python3" shebang without -s >> or -I option. >> >> I propose to deprecate the feature and remove it in Python 4.0. > > Where would pip install --user put packages, and how would one run > scripts that require those packages? Right now these things Just > Work; I've never had to learn how to use virtual environments.
I see two option: 1) "pip install --user" is no longer supported. You have to learn how to use virtual envs. It's really easy: "python3 -m venv path; path/bin/pip install package".
Easy for whom? C, Ruby, JavaScript users, random grandmas and grandpas? Please don't make innocent hate Python, and don't make developers who chose Python to develop software hate it for impossibility to provide decent user support for their software.
-- Best regards, Paul mailto:pmiscml at gmail.com
- Previous message (by thread): [Python-Dev] Deprecate PEP 370 Per user site-packages directory?
- Next message (by thread): [Python-Dev] Deprecate PEP 370 Per user site-packages directory?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]