[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

invention by doko for Debian. Maybe you could get more feedback from other Python packagers on the distutils-sig, python-dev or distributi...@freedesktop.org mailing list? -- components: +Distutils2 nosy: +alexis, barry, brett.cannon, carljm, doko, eric.araujo title: vendor-packages directory

[issue1298835] vendor-packages directory.

Danek Duvall duv...@comfychair.org added the comment: So this has come up again within the Solaris group. Since Rich's original request, we've been using a vendor-packages.pth file in the site-packages directory, which enables the vendor-packages directory. However, I have a concern

[issue1298835] vendor-packages directory.

Terry J. Reedy tjre...@udel.edu added the comment: Further review never happened. Should be close this? -- versions: +Python 3.2 -Python 2.7, Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1298835

[issue1298835] vendor-packages directory.

Changes by Georg Brandl ge...@python.org: -- assignee: - tarek nosy: +tarek ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1298835 ___ ___

[issue1298835] vendor-packages directory.

Daniel Diniz aja...@gmail.com added the comment: Should be considered for 3.1 and 2.7. -- nosy: +ajaksu2 type: - feature request versions: +Python 2.7, Python 3.1 -Python 2.4 ___ Python tracker rep...@bugs.python.org

Re: vendor-packages directory

Terry Reedy wrote: Rich Burridge [EMAIL PROTECTED] wrote in message Until now we've been using /usr/lib/python2.4/site-packages as the directory to install the various Python files that these packages use. My impression is that this is exactly the intended place for general-use support

vendor-packages directory

/lib/python2.4/vendor-packages directory and put out files under there, but what I don't like about it is that it doesn't just work. In other words, it's not one of the known places that Python will look for library or application Python files. I don't think it's reasonable to make developers who

Re: vendor-packages directory

On Tuesday 20 September 2005 10:22, Rich Burridge wrote: [lots of well-written and logical information about a proposed vendor-packages directory snipped] Is this something that would be considered for a future Python release? +1 to that from me... it looks like good idea - have you

Re: vendor-packages directory

Rich: You made it to the States, then? How ironic, I've just been working in VA for nine years, but recently returned to Scotland and ended up living in Linlithgow, known to most Sun long-timers. Hope mp is still providing good service. Rich Burridge wrote: Hi, I work in the Accessibility

Re: vendor-packages directory

Rich Burridge [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] I work in the Accessibility Program Office at Sun Microsystems. I'm part of a team that is using Python to create a screen reader called Orca, that'll help blind people (and people with low vision) have access to the