| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Testing: test_array.py was also extended to check that one can set the
full range of values for each of the integral signed and unsigned
array types.
This closes SourceForge patch #100506.
|
|
|
|
| |
Updated test output.
|
|
|
|
|
| |
Added tests for the new Unicode character name support in the
standard unicode-escape codec.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch adds the openpty() and forkpty() library calls to posixmodule.c,
when they are available on the target
system. (glibc-2.1-based Linux systems, FreeBSD and BSDI at least, probably
the other BSD-based systems as well.)
Lib/pty.py is also rewritten to use openpty when available, but falls
back to the old SGI method or the "manual" BSD open-a-pty
code. Openpty() is necessary to use the Unix98 ptys under Linux 2.2,
or when using non-standard tty names under (at least) BSDI, which is
why I needed it, myself ;-) forkpty() is included for symmetry.
|
|
|
|
|
|
|
| |
<skip@mojam.com>. Revisions to the markup to make it pass LaTeX, added
an index entry and a reference from the sys.exitfunc documentation.
This closes SourceForge patch #100620.
|
| |
|
|
|
|
| |
'link_shared_object()'.
|
|
|
|
|
|
|
| |
methods (but not 'link_executable()', hmmm). Currently only used by
BCPPCompiler; it's a dummy parameter for UnixCCompiler and MSVCCompiler.
Also added 'bcpp' to compiler table used by 'new_compiler()'.
|
| |
|
|
|
|
|
|
|
|
| |
Two major points:
* lots of overlap with MSVCCompiler; the common code really should be
factored out into a base class, say WindowsCCompiler
* it doesn't work: weird problem spawning the linker (see comment for
details)
|
|
|
|
|
| |
command objects.
Various formatting tweaks, typo fixes in comments.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Ditched my old code that fixed relative paths in the Makefile -- didn't work,
doomed to failure, etc.
|
|
|
|
| |
the 'implib_dir' attribute is back (only on NT, of course).
|
|
|
|
|
|
| |
Also supposedly made some change to where .lib files wind up under MSVC++,
but I don't understand how to code is doing what Thomas says it's
doing.
|
| |
|
| |
|
|
|
|
|
| |
Added 'check_lib()', which provides a subset of the functionality of
'check_func()' with a simpler interface and implementation.
|
| |
|
|
|
|
| |
and I lack the time to track down the cause.
|
|
|
|
| |
parsing the sample data once with 8-bit strings and once with Unicode.
|
| |
|
| |
|
| |
|
|
|
|
| |
connections.
|
| |
|
|
|
|
|
| |
doesn't blow up. We don't currently use the 'set_executables()' bureaucracy,
although it would be nice to do so for consistency with UnixCCompiler.
|
|
|
|
| |
Ensure that 'extra_args' (whether compile or link args) is never None.
|
|
|
|
|
|
| |
to 'msvc_prelink_hack()', adding the parameters that it actually needs,
and only calling it for MSVC compiler objects. Generally gave up on the
idea of a general "hook" mechanism: deleted the empty 'precompile_hook()'.
|
| |
|
| |
|
|
|
|
|
| |
experimental and untested.)
Call 'customize_compiler()' after getting CCompiler object.
|
|
|
|
|
|
| |
information about building Python extensions that we discovered in
Python's makefile. Currently only needed on Unix, so does nothing on
other systems.
|
|
|
|
|
|
|
|
|
|
|
| |
that a particular compiler system depends on. This consists of the
'set_executables()' and 'set_executable()' methods, and a few lines in
the constructor that expect implementation classes to provide an
'executables' attribute, which we use to initialize several instance
attributes. The default implementation is somewhat biased in favour of
a Unix/DOS "command-line" view of the world, but it shouldn't be too
hard to override this for operating systems with a more sophisticated
way of representing programs-to-execute.
|
|
|
|
|
|
|
|
| |
meant playing along with the new "dictionary of executables" scheme
added to CCompiler by adding the 'executables' class attribute, and
changing all the compile/link/etc. methods to use the new attributes
(which encapsulate both the program to run and its standard arguments,
so it was a *little* bit more than just changing some names).
|
|
|
|
|
| |
Unix shell-like syntax (eg. in Python's Makefile, for one thing -- now that
I have this function, I'll probably allow quoted strings in config files too.
|
|
|
|
| |
Fixed a few comments.
|
|
|
|
| |
Tweaked help text.
|
|
|
|
|
|
| |
the "install_data" command to the installation base, which is usually just
sys.prefix. (Any setup scripts out there that specify data files will have
to set the installation directory, relative to the base, explicitly.)
|
|
|
|
| |
on if it sees a filename with unknown extension.
|
|
|
|
|
|
|
| |
in the module of the command classes that have command-specific
help options. This lets us keep the principle of lazily importing
the ccompiler module, and also gets away from defining non-methods
at class level.
|
| |
|
| |
|
| |
|
|
|
|
| |
accomodate SWIG interface files, resource files, etc.).
|
|
|
|
| |
than a boolean indicating whether it did the copy.
|
|
|
|
| |
Made codecs.open() default to 'rb' as file mode.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These two fixes were approved by me.
Peter Kropf:
There's a problem with the xmllib module when used with JPython. Specifically,
the JPython re module has trouble with the () characters in strings passed into
re.compile.
Spiros Papadimitriou:
I just downloaded xmllib.py ver. 0.3 from python.org and there
seems to be a slight typo: Line 654 ("tag = self.stack[-1][0]"
in parse_endtag), is indented one level more than it should be.
I just thought I'd let you know...
|