1 This is the "zetuptoolz" fork of setuptools. This version is forked from
2 setuptools trunk r80621 (which is current as of 2010-08-31), with the following
6 * Zooko's patches for the following bugs and features have been applied:
8 <http://bugs.python.org/setuptools/issue17>
9 "easy_install will install a package that is already there"
11 <http://bugs.python.org/setuptools/issue54>
12 "be more like distutils with regard to --prefix="
14 <http://bugs.python.org/setuptools/issue53>
15 "respect the PYTHONPATH"
16 (Note: this patch does not work as intended when site.py has been modified.
17 This will be fixed in a future version.)
20 * The following patch to setuptools introduced bugs, and has been reverted
24 ------------------------------------------------------------------------
25 r45514 | phillip.eby | 2006-04-18 04:03:16 +0100 (Tue, 18 Apr 2006) | 9 lines
27 Backport pkgutil, pydoc, and doctest from the 2.5 trunk to setuptools
28 0.7 trunk. (Sideport?) Setuptools 0.7 will install these in place of
29 the 2.3/2.4 versions (at least of pydoc and doctest) to let them work
30 properly with eggs. pkg_resources now depends on the 2.5 pkgutil, which
31 is included here as _pkgutil, to work around the fact that some system
32 packagers will install setuptools without overriding the stdlib modules.
33 But users who install their own setuptools will get them, and the system
34 packaged people probably don't need them.
35 ------------------------------------------------------------------------
38 * If unpatched setuptools decides that it needs to change an existing site.py
39 file that appears not to have been written by it (because the file does not
40 start with "def __boot():"), it aborts the installation.
41 zetuptoolz leaves the file alone and outputs a warning, but continues with
45 * The scripts written by zetuptoolz have the following extra line:
47 # generated by zetuptoolz <version number>
52 * Windows-specific changes (native Python):
54 Python distributions may have command-line or GUI scripts.
55 On Windows, setuptools creates an executable wrapper to run each
56 script. zetuptools uses a different approach that does not require
57 an .exe wrapper. It writes approximately the same script file that
58 is used on other platforms, but with a .pyscript extension.
59 It also writes a shell-script wrapper (without any extension) that
60 is only used when the command is run from a Cygwin shell.
62 Some of the advantages of this approach are:
64 * Unicode arguments are preserved (although the program will
65 need to use some Windows-specific code to get at them in
66 current versions of Python);
67 * it works correctly on 64-bit Windows;
68 * the zetuptoolz distribution need not contain either any
69 binary executables, or any C code that needs to be compiled.
71 See setuptools\tests\win_script_wrapper.txt for further details.
73 Installing or building any distribution on Windows will automatically
74 associate .pyscript with the native Python interpreter for the current
75 user. It will also add .pyscript and .pyw to the PATHEXT variable for
76 the current user, which is needed to allow scripts to be run without
79 There is an additional setup.py command that can be used to perform
80 these steps separately (which isn't normally needed, but might be
81 useful for debugging):
83 python setup.py scriptsetup
85 Adding the --allusers option, i.e.
87 python setup.py scriptsetup --allusers
89 will make the .pyscript association and changes to the PATHEXT variable
90 for all users of this Windows installation, except those that have it
91 overridden in their per-user environment. In this case setup.py must be
92 run with Administrator privileges, e.g. from a Command Prompt whose
93 shortcut has been set to run as Administrator.