[Python-Dev] Python install layout and the PATH on win32 (Rationale part 1: Regularizing the layout) (original) (raw)
PJ Eby pje at telecommunity.com
Sat Mar 24 04:21:18 CET 2012
- Previous message: [Python-Dev] Python install layout and the PATH on win32 (Rationale part 1: Regularizing the layout)
- Next message: [Python-Dev] Python install layout and the PATH on win32 (Rationale part 1: Regularizing the layout)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mar 23, 2012 4:19 PM, "VanL" <van.lindberg at gmail.com> wrote:
Three notes. FIrst, distutils.cfg doesn't always work because it is centered around the idea of set paths that are the same each time - which doesn't always work with virtualenvs.
And the virtualenv doesn't contain its own copy of distutils.cfg?
Second, most installer tools don't follow distutils.cfg. Even if that helps for python setup.py install, the other tools are still broken when you want to specify a layout.
So, we should change Python to fix the broken tools that don't follow documented standards for configuring installation locations?
If the tools are that broken, aren't they going to break even harder when you change the paths for Windows?
And fourth, (because nobody expects the spanish inquisition), isn't the gratuitous difference a (small but) obvious wart?
It's hardly the only wart we keep around for backwards compatibility. If it's going to change, it needs a proper transition period at the least. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20120323/868fb97f/attachment.html>
- Previous message: [Python-Dev] Python install layout and the PATH on win32 (Rationale part 1: Regularizing the layout)
- Next message: [Python-Dev] Python install layout and the PATH on win32 (Rationale part 1: Regularizing the layout)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]