| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
present - at least the swigged file should be named <name>_wrap.c as
this is also SWIG's default. (Even better would be to generate the
wrapped sources in a different location, but I'll leave this for
later).
Newer versions of SWIG don't accept the -dnone flag any more.
Since virtually nobody uses SWIG with distutils, this should do no
harm.
Suggested be Martin Bless on c.l.p.
|
| |
|
|
|
|
|
|
| |
Question for Jack Jansen: is this reasonable?
Candidate for 2.2 release branch (if Jack thinks it's OK).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
searched for a dependency for runtime linking.
This closes SF bug #445902.
|
|
|
|
| |
[ #409430 ] pydoc install broken
|
|
|
|
|
|
|
|
| |
[ #477371 ] build_scripts can use wrong #! line
scripts now get "built" into a directory
build/scripts-$(PYTHON_VERSION)/
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
adjust it when a versioned interpreter is supplied (#!.../python2 ...)
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
invalid filenames on Windows when building without specifying a
version number in the setup script.
See also
http://mail.python.org/pipermail/distutils-sig/2001-November/002656.html
Bugfix candidate.
|
| |
|
|
|
|
| |
Tom Loredo.
|
| |
|
|
|
|
|
| |
in the gui.
Updated to include the new exe-file.
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
This will have to stay until we decide to drop 1.5.2 compatibility
completely.
|
|
|
|
| |
Slightly modified version of patch from Jon Nelson (jnelson).
|
|
|
|
|
| |
INSTALLED_FILES output. Modified version of a patch from
Jon Nelson (jnelson)
|
|
|
|
| |
Fixed.
|
| |
|
|
|
|
| |
the setup script is running from inside Vim.
|
|
|
|
|
| |
'static' and 'shared'. This fixes extension building for dynamic
Pythons on MacOSX.
|
|
|
|
|
|
| |
modules and extensions on Windows is now $PREFIX/Lib/site-packages.
Includes backwards compatibility code for pre-2.2 Pythons. Contributed
by Paul Moore.
|
|
|
|
| |
I have no way of testing this.
|
|
|
|
| |
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
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Use construction-syntax for an exception to make the argument easier
to read.
|
| |
|
|
|
|
|
|
|
| |
though 'licence' is still supported for backward-compatibility
(Should I add a warning to get_licence(), or not bother?)
Also fixes an UnboundLocalError noticed 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
|
|
|
|
| |
do it back in copy_file() (not at module level).
|
|
|
|
|
| |
distutils.util.get_platform() problems caused by the cruft contained
in Cygwin's uname -s.
|
| |
|
| |
|