| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
From SF patch #736962.
|
|
|
|
|
|
| |
The compiler was reseting the list comprehension tmpname counter for each function, but the symtable was using the same counter for the entire module. Repair by move tmpname into the symtable entry.
Bugfix candidate.
|
|
|
|
|
|
| |
(code coverage for Modules/arraymodule.c is at 91%)
From SF patch #736962.
|
|
|
|
| |
tests and comments.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
getpwnam()/getpwuid() return consistent data.
Change test_grp to check that getgrall() and
getgrnam()/getgrgid() return consistent data.
Add error checks similar to test_pwd.py.
Port test___all__.py to PyUnit.
From SF patch #662807.
|
|
|
|
|
| |
cases increasing coverage in unicodedata.c from 87% to 95%
(when the normalization tests are run). From SF patch #662807.
|
|
|
|
|
|
|
| |
between str, unicode, UserString and the string module
as possible. This increases code coverage in stringobject.c
from 83% to 86% and should help keep the string classes
in sync in the future. From SF patch #662807
|
|
|
|
|
|
| |
Mostly rename WARN -> WARNING
Other misc tweaks
Update tests (not in original patch)
|
| |
|
|
|
|
|
|
|
|
| |
extension implemented flush() was fixed. Scott also rewrite the
zlib test suite using the unittest module. (SF bug #640230 and
patch #678531.)
Backport candidate I think.
|
| |
|
|
|
|
| |
The test no longer produces output with \r\n in it.
|
| |
|
|
|
|
|
|
| |
cases and a few methods. This increases code coverage
in Objects/unicodeobject.c from 81% to 85%.
(From SF patch #662807)
|
|
|
|
|
|
|
|
| |
port the tests to PyUnit and add many tests for error
cases. This increases code coverage in Python/bltinmodule.c
from 75% to 92%. (From SF patch #662807, with
assert_(not fcmp(x, y)) replaced with assertAlmostEqual(x, y)
where possible)
|
| |
|
| |
|
|
|
|
| |
Add a test for logging from Vinay Sajip (module author)
|
|
|
|
| |
with sequences.
|
| |
|
|
|
|
| |
Verify that the lookup for an existing name succeeds.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
sys.getwindowsversion() on Windows (new enahanced Tim-proof <wink>
version), and fix test_pep277.py in a few minor ways.
Including doc and NEWS entries.
|
| |
|
|
|
|
|
| |
Raise ValueError if user passes a size to mmap which is larger
than the file.
|
|
|
|
|
| |
missing key. (Also added a guard to SyntaxError__str__ to prevent
calling PyString_Check(NULL).)
|
|
|
|
|
|
| |
the tokenize module by test_tokenize.py. The FutureWarnings only
appeared during installation, and I've figured out a way to suppress
those in a different way.
|
|
|
|
| |
trailing `L's.
|
|
|
|
| |
also drop the output file.
|
|
|
|
|
|
|
|
|
|
|
| |
existed at the time atexit first got imported. That's a bug, and this
fixes it.
Also reworked test_atexit.py to test for this too, and to stop using
an "expected output" file, and to test what actually happens at exit
instead of just simulating what it thinks atexit will do at exit.
Bugfix candidate, but it's messy so I'll backport to 2.2 myself.
|
|
|
|
|
|
|
|
|
|
| |
If multiple header fields with the same name occur, they are combined
according to the rules in RFC 2616 sec 4.2:
Appending each subsequent field-value to the first, each separated by
a comma. The order in which header fields with the same field-name are
received is significant to the interpretation of the combined field
value.
|
|
|
|
| |
Document toprettyxml.
|
|
|
|
| |
timing information in the output makes the determination of success bogus.
|
| |
|
|
|
|
| |
Changed test_timeout.py to conform to the guidelines in Lib/test/README.
|
| |
|
|
|
|
|
|
| |
Also add a test that Python doesn't die with SIGXFSZ if it exceeds the
file rlimit. (Assuming this will also test the behavior when the 2GB
limit is exceed on a platform that doesn't have large file support.)
|
|
|
|
| |
Related to SF bug #505315
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
PEP 285. Everything described in the PEP is here, and there is even
some documentation. I had to fix 12 unit tests; all but one of these
were printing Boolean outcomes that changed from 0/1 to False/True.
(The exception is test_unicode.py, which did a type(x) == type(y)
style comparison. I could've fixed that with a single line using
issubtype(x, type(y)), but instead chose to be explicit about those
places where a bool is expected.
Still to do: perhaps more documentation; change standard library
modules to return False/True from predicates.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
457466: popenx() argument mangling hangs python
226766: popen('python -c"...."') tends to hang
Fixes argument quoting in w9xpopen.exe for Windows 9x. w9xpopen.exe
also never attempts to display a MessageBox when not executed
interactively.
Added test_popen() test. This test currently just executes
"python -c ..." as a child process, and checks that the expected
arguments were all recieved correctly by the child process. This
test succeeds for me on Win9x, win2k and Linux, and I hope it does
for other popen supported platforms too :)
|
| |
|
|
|
|
| |
Closes SF patch 494871.
|