Fix for sf # 749210, wininst isn't build correctly after building zip.
The problem was that subcommands were not reinitialized.
Bugfix candidate, will backport myself.
(no idea why, or how)
backport theller's patch
Set the warn_dir option to 0 before running the install command.
This suppresses bogus warnings about modules installed into a directory
not in sys.path.
Bugfix candidate.
SF bug 543840: complex(string) accepts strings with \0
complex_subtype_from_string(): this stopped parsing at the first 0
byte, as if that were the end of the input string.
revision 1.63 of install.py
Revert part of previous patch: several install_* subcommands expect
.compile to be None, and set it to true if it is.
Caught by Pearu Peterson.
Bugfix candidate, if the previous change is accepted for
release22-maint.
revision 1.62 of install.py
Add missing Boolean options
Remove unused no_compile flag
Initialize the Boolean attribute .compile to 0 instead of None
Bugfix candidate.
backport akuchling's checkin of
revision 1.30 of bdist_wininst.py
Add unlisted Boolean options. Thomas H., can you please check that I
got this right?
Bugfix candidate, unless Thomas notes a problem.
revision 1.28 of bdist_rpm.py
[Bug #517451] bdist_rpm didn't list all of its Boolean options.
(Someone should check the other commands for this same error.)
Bugfix candidate.
revision 1.11 of install_scripts.py
Restrict the mode to the lowest four octal positions; higher positions
contain the type of the file (regular file, socket, link, &c.).
This means that install_scripts will now print
"changing mode of <file> to 775" instead of "... to 100775".
2.2 bugfix candidate, I suppose, though this isn't actually fixing a bug.
This patch was applied by an alarmingly automated system -- I hope it
worked...
package_dir must be converted from the distutils path conventions to
local conventions before being used by build_py.
Fixes SF bug #509288, probably a candidate for 2.2.1
crashes.
If no external zip-utility is found, the archive is created by the
zipfile module, which behaves different now than in 2.1: if the
zip-file is created in the root directory if the distribution, it will
contain an (empty) version of itself.
This triggered the above bug - so it's better to create the zip-file
far away in the TMP directory.
>
> When using 'distutils' (shipped with Python 2.1) I've found that my
> Python scripts installed with a first line of:
>
> #!/usr/bin/python2.1None
>
> This is caused by distutils trying to patch the first line of the python
> script to use the current interpreter.
distutils for the library modules built as shared objects. A better solution
appears possible, but with the threat that the distutils becomes more
magical ("complex").
This closes SF bug #458343.
bdist_wininst doesn't use the NT SCHEME any more, instead
a custom SCHEME is used, which is exchanged at installation
time, depending on the python version used.
Avoid a bogus warning frpom install_lib about installing
into a directory not on sys.path.
