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

Steve Dower steve.dower at python.org
Sat Jan 13 15:55:24 EST 2018

I’m generally +1, though I don’t see an easy migration path. Moving to a node.js project model might be feasible, but I suspect our real solution will end up having to be ensuring use of -s where it’s needed.

Top-posted from my Windows phone

From: Christian Heimes Sent: Sunday, January 14, 2018 4:09 To: python-dev at python.org Subject: [Python-Dev] Deprecate PEP 370 Per user site-packages directory?

Hi,

PEP 370 [1] was my first PEP that got accepted. I created it exactly one decade and two days ago for Python 2.6 and 3.0. Back then we didn't have virtual environment support in Python. Ian Bicking had just started to create the virtualenv project a couple of months earlier.

Fast forward 10 years...

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.

Regards, Christian

[1] https://www.python.org/dev/peps/pep-0370/

Python-Dev mailing list Python-Dev at python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/steve.dower%40python.org

-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20180114/8390311e/attachment.html>

More information about the Python-Dev mailing list