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