[Python-Dev] Python install layout and the PATH on win32 (Rationale part 1: Regularizing the layout)
PJ Eby
pje at telecommunity.com
Fri Mar 23 17:39:41 CET 2012
More information about the Python-Dev mailing list
Fri Mar 23 17:39:41 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 22, 2012 2:57 PM, "VanL" <van.lindberg at gmail.com> wrote: > That said, while I think that the above is a good idea, my personal ambitions are more modest: If the names of the top-level directories only were changed to 'bin', 'lib', and 'include' - never mind differences under 'lib' - I would be happy. In fact, even the one change of 'Scripts' to 'bin' everywhere would get 90% of my uses. Why don't you just install your scripts to 'bin' everywhere then, and add the bin directory to the path on Windows? Distutils allows you to customize your install target for scripts, as does setuptools. Why do you need *Python's own default* to change, to support your preference for using a bin directory? Even if you are using tools that don't use distutils' configuration settings for these directories, why not simply fix those tools so that they do? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20120323/684ce58e/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 ]
More information about the Python-Dev mailing list