| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
Slightly modified version of patch from Jon Nelson (jnelson).
|
| |
|
|
|
| |
INSTALLED_FILES output. Modified version of a patch from
Jon Nelson (jnelson)
|
| |
|
|
|
|
| |
modules and extensions on Windows is now $PREFIX/Lib/site-packages.
Includes backwards compatibility code for pre-2.2 Pythons. Contributed
by Paul Moore.
|
| |
|
|
| |
Add executable extension, needed to get the program name right on Win32
|
| |
|
|
|
| |
Provide include_dirs argument to all calls to ._preprocess and ._compile
Fix typo: pattern.search(pattern) should be pattern.search(line)
|
| |
|
|
| |
(This command seems to be essentially untested; should fix that...)
|
| |
|
|
|
|
| |
libraries. This is done by adding a .get_source_files() method,
contributed by Rene Liebscher and slightly modified.
Remove an unused local variable spotted by PyChecker
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
under MacOS.)
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
to the current Python interpreter (ie. the one used for
building/installation), even (especially!) if "/usr/bin/env" appears in
the #! line.
Rationale: installing scripts with "#!/usr/bin/env python" is asking for
trouble, because
1) it might pick the wrong interpreter (not the one used to
build/install the script)
2) it doesn't work on all platforms (try it on IRIX 5, or on Linux
with command-line options for python)
3) "env" might not be in /usr/bin
|
| | |
|
| | |
|
| |
|
|
| |
rebuild.
|
| | |
|
| |
|
|
|
| |
specified on the command-line or in setup.cfg. The option processing
leaves them as strings, but they're supposed to be lists.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
has been changed to include an uninstaller.
I forgot to mention in the uninstaller checkin that the logfile
name (used for uninstalling) has been changed from
<module>.log to <module>-wininst.log. This should prevent
conflicts with a distutils logfile serving the same purpose.
The short form of the --bdist-dir (-d) option has been removed
because it caused conflicts with the short form of the --dist-dir
option.
|
| | |
|
| |
|
|
|
| |
slightly more brief, and more like the message that an extension will not
be built because the built copy is up to date.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
--bitmap command line option allows to use a different bitmap file instead
of the build-in python powered logo.
--title lets you specify the text to display on the background.
The editbox in the first screen now longer is
selected (highlighted), it had the WS_TABSTOP flag.
This is the patch
http://sourceforge.net/patch/?func=detailpatch&patch_id=103687&group_id=5470
with two changes:
1. No messagebox displayed when the compilation to .pyc or .pyo files
failes, this will only confuse the user (and it will fail under certain
cases, where sys.path contains garbage).
2. A debugging print statement was removed from bdist_wininst.py.
|
| |
|
|
| |
This partially fixes bug #128930.
|
| |
|
|
| |
Uche Ogbuji
|
| | |
|
| |
|
|
| |
building.
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
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.
|
| |
|
|
| |
os.pathsep
|
| |
|
|
| |
DISTUTILS_DEBUG set"
|
| | |
|
| |
|
|
| |
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
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
| |
'util.byte_compile()'. Currently just reproduces the existing functionality
-- doesn't use any of the fancy features in the new 'byte_compile()'.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
on the module file -- could be useful for subclasses overriding it.
|