[Python-Dev] Deprecate PEP 370 Per user site-packages directory? (original) (raw)

Antoine Pitrou solipsis at pitrou.net
Sat Jan 13 15:12:43 EST 2018

On Sat, 13 Jan 2018 21:06:19 +0100 Christian Heimes <christian at python.org> wrote:

>> >> 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". >> 2) "pip install --user" automatically creates or uses a custom virtual >> (~/.pip/virtualenv-$VERSION/) and links entry points to ~/.local/bin. > > Option 2 doesn't work, since the installed package then isn't known to > the system Python.

I see that as a benefit. User installed packages will no longer be able to break system-wide programs.

I don't know if it's better or worse. I'm just saying it's not a migration path from user site-packages since it doesn't have the same semantics.

These days a lot of packages are using setuptools' entry points to create console scripts. Entry point have no option to create a console script with -s or -I flag.

Perhaps that should be fixed.

Regards

Antoine.

More information about the Python-Dev mailing list