| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
the resulting path is empty.
|
| |
|
|
|
|
| |
building.
|
|
|
|
|
|
|
|
|
| |
prevent binding for str from masking use of builtin str in nested
function.
(This is the only case I found in the standard library where a local
shadows a global or builtin. There may be others, but the regression
test doesn't catch them.)
|
| |
|
|
|
|
|
|
|
|
|
| |
Lib/distutils/command/build_ext.py(build_ext.finalize_options): Add
Cygwin specific code to append Python's library directory to the
extension's list of library directories.
(build_ext.get_libraries): Add Cygwin specific code to append Python's
(import) library to the extension's list of libraries.
|
|
|
|
|
|
| |
This patch adds support for Cygwin to util.get_platform(). A Cygwin
specific case is needed due to the format of Cygwin's uname command,
which contains '/' characters.
|
|
|
|
|
|
|
|
| |
sys.prefix + 'config/Makefile'. When building Python for the first
time, these files aren't there, so the files from the build tree have
to be used instead; this file adds an entry point for specifying that
the build tree files should be used. (Perhaps 'set_python_build' should
should be preceded with an underscore?)
|
|
|
|
|
|
|
|
|
|
| |
for done[n] can be integers as well as strings, but the code
concatenates them with strings (fixed by adding a str()) and calls
string.strip() on them (fixed by rearranging the logic)
(Presumably this wasn't noticed previously because parse_makefile()
was only called on Modules/Makefile, which contains no integer-valued
variables.)
|
|
|
|
|
|
|
| |
produce a list of unique filenames:
"While attempting to build an RPM using distutils on Python 2.0,
rpm complained about duplicate files. The following patch fixed
that problem.
|
|
|
|
|
| |
prevent creating files such as build/lib.whatever/Modules/foo.o
when given a source filename such as Modules/foo.c.
|
|
|
|
|
| |
to the Distutils-SIG and archived at
http://mail.python.org/pipermail/distutils-sig/2000-November/001755.html
|
| |
|
|
|
|
| |
os.pathsep
|
|
|
|
| |
DISTUTILS_DEBUG set"
|
|
|
|
|
| |
Use != instead of <> since <> is documented as "obsolescent".
Use "is" and "is not" when comparing with None or type objects.
|
|
|
|
|
| |
use it to generate a dialog for users to specify the command-line (because
providing a command-line with MacPython is so awkward).
|
| |
|
| |
|
| |
|
|
|
|
| |
an 'other_libraries()' parameter.
|
|
|
|
| |
we actually installed modules to a directory in sys.path.
|
| |
|
|
|
|
|
| |
This should close SF bug (patch)
http://sourceforge.net/patch/?func=detailpatch&patch_id=101844&group_id=5470
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
about how it would be nice to write absolute paths to the temporary
byte-compilation script, but this doesn't work because it screws up the
trailing-slash trickery done to 'prefix' in build_py's 'byte_compile()'
method.
Fixed to use 'execute()' instead of 'os.remove()' to remove the temporary
script: now it doesn't blow up in dry-run mode!
|
| |
|
|
|
|
|
|
|
|
|
| |
by default (since compiling at install time works just fine). Details:
- added 'compile' and 'optimize' options
- added 'byte_compile()' method
- changed 'get_outputs()' so it includes bytecode files
A lot of the code added is very similar to code in install_lib.py;
would be nice to factor it out further.
|
|
|
|
| |
instruct the "install_lib" command from the command-line.
|
|
|
|
|
|
|
|
|
|
|
|
| |
choice between (compile, no-compile) * (optimize=0, optimize=1,
optimize=2). Details:
- added --no-compile option to complement --compile, which has
been there for ages
- changed --optimize (which never worked) to a value option, which
expects 0, 1, or 2
- renamed 'bytecompile()' method to 'byte_compile()', and beefed
it up to handle both 'compile' and 'optimize' options
- fix '_bytecode_filenames()' to respect the new options
|
| |
|
|
|
|
| |
pure Python modules to compile.
|
|
|
|
| |
blowing up.
|
|
|
|
|
| |
'util.byte_compile()'. Currently just reproduces the existing functionality
-- doesn't use any of the fancy features in the new 'byte_compile()'.
|
|
|
|
|
|
|
|
|
|
| |
standard 'py_compile.compile()' function. Laundry list of features:
- handles standard Distutils 'force', 'verbose', 'dry_run' flags
- handles various levels of optimization: can compile directly in
this interpreter process, or write a temporary script that is
then executed by a new interpreter with the appropriate flags
- can rewrite the source filename by stripping an optional prefix
and preprending an optional base dir.
|
|
|
|
|
|
| |
Fixed 'subst_vars()' so it actually blows up like the docstring claims
(and fixed the docstring not to claim it handles ${var}, which it
doesn't).
|
| |
|
| |
|
|
|
|
|
| |
absolute pathnames; this lets it keep working in the face of chdir'ing
around.
|
| |
|
| |
|
|
|
|
| |
on the module file -- could be useful for subclasses overriding it.
|
|
|
|
| |
this will please everyone (as if that's possible).
|
|
|
|
| |
'uname()' -- specifically NeXTSTEP.
|
|
|
|
|
|
| |
- added 'sub_commands' class attr
- added 'has_*()' predicates referenced by the sub-command list
- rewrote 'run()' so it's a trivial loop over relevant sub-commands
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
They are unneeded: All this stuff is already done by the
install command which is run by bdist_wininst.
One bug has been fixed:
The root of the fake install tree is install.install_purelib,
not install.install_lib!
They are different if the extra_path option is used in
the setup function.
Rebuild after the changes to wininst.exe.
|