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

Éric Araujo 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 invention by doko for De

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

Éric Araujo 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. vendor-packages is arguably

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

Terry J. Reedy 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 fine within the co

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

Changes by Trent Nelson : -- nosy: +brian-cameron-oracle, trent ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[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 sp

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

Changes by Éric Araujo : -- components: +Interpreter Core -Distutils2, Library (Lib) versions: +Python 3.4 -Python 3.3 ___ Python tracker ___ __

[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 http:/

[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