[issue1298835] Add a vendor-packages directory for system-supplied modules

Change by Brett Cannon : -- nosy: -brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue1298835] Add a vendor-packages directory for system-supplied modules

Changes by John Beck john.b...@oracle.com: -- nosy: +jbeck ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1298835 ___ ___ Python-bugs-list mailing

[issue1298835] Add a vendor-packages directory for system-supplied modules

Robert Kuska added the comment: Ok, I have started a thread at pypa-devs google group. https://groups.google.com/forum/#!topic/pypa-dev/r6qsAmJl9t0 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1298835

[issue1298835] Add a vendor-packages directory for system-supplied modules

Robert Kuska added the comment: There is ongoing discussion on pip's github tracker [1] about default location where to install user modules. IMO this is something that should be dealt with in Python Interpreter Core [2][3]. I would like to hear some opinion from python devs on this. [1]

[issue1298835] Add a vendor-packages directory for system-supplied modules

Nick Coghlan added the comment: Note that authority over package design decisions has been delegated to the Python Packaging Authority - it's up to them to decide what they want and ask for it (of they decide they actually need modifications to the interpreter), not for Python core to tell

[issue1298835] Add a vendor-packages directory for system-supplied modules

Changes by Piotr Dobrogost p...@bugs.python.dobrogost.net: -- nosy: +piotr.dobrogost ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1298835 ___ ___

[issue1298835] Add a vendor-packages directory for system-supplied modules

Changes by Terry J. Reedy tjre...@udel.edu: -- stage: - patch review versions: +Python 3.5 -Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1298835 ___

[issue1298835] Add a vendor-packages directory for system-supplied modules

Changes by Éric Araujo mer...@netwok.org: -- components: +Interpreter Core -Distutils2, Library (Lib) versions: +Python 3.4 -Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1298835

[issue1298835] Add a vendor-packages directory for system-supplied modules

Éric Araujo added the comment: Adding Nick to this discussion, since distutils-sig is talking about these issues right now. Previous discussions: http://mail.python.org/pipermail/python-list/2005-September/345116.html http://mail.python.org/pipermail/python-dev/2005-September/056682.html

[issue1298835] Add a vendor-packages directory for system-supplied modules

Nick Coghlan added the comment: The discussion on distutils-sig that Éric is referring to is one were I ended up pointing out that PEP 439 (bootstrapping pip in 3.4) needs to address this in some manner, so that pip (which installs to site-packages) doesn't end up fighting with system package

[issue1298835] Add a vendor-packages directory for system-supplied modules

Matthias Klose added the comment: there is more than one thing addressed with the 'dist-packages' choice of name. The primary reason is to have a directory where you only find python packages as distributed by the linux distribution, and where installers do not install to by default. Even if

[issue1298835] Add a vendor-packages directory for system-supplied modules

Bohuslav Slavek Kabrda added the comment: I'm strongly +1 on this one. I package Python RPMs for Fedora and I know what mess can come out of installing through both RPM and easy_install/pip. In Fedora, both Perl and Ruby use vendor specific dirs for installing RPM packaged modules and site

[issue1298835] Add a vendor-packages directory for system-supplied modules

Changes by Trent Nelson tr...@snakebite.org: -- nosy: +brian-cameron-oracle, trent ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1298835 ___ ___

[issue1298835] Add a vendor-packages directory for system-supplied modules

Éric Araujo mer...@netwok.org added the comment: not all OSes have vendors I realized that because French is my native language, I interpret “vendor” as “seller” (the meaning of “vendeur”), but I think that in English it just means “distributor” and has no relation with selling.

[issue1298835] Add a vendor-packages directory for system-supplied modules

Terry J. Reedy tjre...@udel.edu added the comment: In English also, to vend is to sell, direct from Fr. *vendre*. However, ideas are not necessarily sold for money, but for assent, adoption, or other action. My dictionary has 'publish' as a secondary meaning of vend. So 'vendor-packages' is

[issue1298835] Add a vendor-packages directory for system-supplied modules

Éric Araujo mer...@netwok.org added the comment: Thanks for detailing the rationale. Separating the “vendor”-controlled space (or let’s call it system; not all OSes have vendors :) from the sysadmin-controlled location is indeed a real concern, as shown by the recent-ish dist-packages