| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
It's guaranteed now, assuming the platform modf() works correctly.
|
|
|
|
| |
wide builds.
|
| |
|
|
|
|
|
| |
Heavily modified so this doesn't break on Windows.
This closes SF patch #441175.
|
|
|
|
| |
Note: This test fails on Windows. Don't know why yet.
|
|
|
|
| |
This closes SF patch #440291.
|
|
|
|
| |
This closes SF patch #440290.
|
| |
|
|
|
|
|
|
| |
+ test_quopri.py relied on significant trailing spaces. Fixed.
+ test_dircache.py (still) doesn't work on Windows (directory mtime on
Windows doesn't work like it does on Unix).
|
| |
|
|
|
|
|
|
|
|
| |
correctly and thus roundtrip-safe.
Some minor cleanups of the code.
Added tests for the roundtrip-safety.
|
|
|
|
|
| |
Modified by Fred Drake.
This closes SF patch #440827.
|
|
|
|
| |
This closes SF patch #440826.
|
| |
|
|
|
|
| |
expected-output file.
|
|
|
|
| |
This closes SF bug #440351. It should not be moved to Python 2.1.1.
|
|
|
|
| |
all platforms that offer tempnam().
|
|
|
|
|
| |
file management functions that have just been made available on more
platforms.
|
|
|
|
| |
no reason to pretend the syntax trees we're dealing with are abstract.
|
|
|
|
| |
(Should be merged with descr branch.)
|
|
|
|
| |
great, it's your turn to watch it fail for months <0.9 wink>.
|
|
|
|
|
|
|
|
| |
was already correctly parsed (contrary to a comment in Mailman).
test_rfc2822_phrases(): RFC 2822 now requires that we allow `.' in
phrases, which means we must accept dots in unquoted realname parts.
Add a test to check the change in rfc822.py 1.58.
|
|
|
|
| |
Based on the test for the HTMLParser module.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
that info to code dynamically compiled *by* code compiled with generators
enabled. Doesn't yet work because there's still no way to tell the parser
that "yield" is OK (unlike nested_scopes, the parser has its fingers in
this too).
Replaced PyEval_GetNestedScopes by a more-general
PyEval_MergeCompilerFlags. Perhaps I should not have? I doubted it was
*intended* to be part of the public API, so just did.
|
|
|
|
| |
test.
|
|
|
|
| |
simplified and generalized to rectangular boards.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
an exception.
|
|
|
|
|
| |
New test_fileinput.py from Nick Mathewson, fiddled to use TESTFN and sundry
style nits.
|
|
|
|
|
| |
New test_uu.py from Nick Mathewson, fiddled to work on Windows too.
Somebody should check that it still works on non-Windows boxes, though!
|
|
|
|
|
|
| |
- Set the host to "localhost" instead of "".
- Skip the AF_UNIX tests when socket.AF_UNIX is not defined.
|
|
|
|
|
|
|
|
|
| |
fixed. Regrettably, this must be run manually -- somehow the I/O
redirection of the regression test breaks the test. When run under
the regression test, this raises ImportError with a warning to that
effect.
Bugfix candidate!
|
|
|
|
|
|
|
| |
name when filling in the internal data structures, otherwise we incorrectly
raise a KeyError.
This fixes SF bug #432369.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
solver. In conjunction, they easily found a tour of a 200x200 board:
that's 200**2 == 40,000 levels of backtracking. Explicitly resumable
generators allow that to be coded as easily as a recursive solver (easier,
actually, because different levels can use level-customized algorithms
without pain), but without blowing the stack. Indeed, I've never written
an exhaustive Tour solver in any language before that can handle boards so
large ("exhaustive" == guaranteed to find a solution if one exists, as
opposed to probabilistic heuristic approaches; of course, the age of the
universe may be a blip in the time needed!).
|
|
|
|
|
| |
sure about this one, but test #133283 now works even with the fix in
place, and so does the test suite. we'll see what comes up...
|
|
|
|
|
| |
This is another one that leaks memory without an explict clear! Time to
bite this bullet.
|
|
|
|
| |
and fiddle the conjoin tests to exercise all the new possible paths.
|
|
|
|
|
|
|
|
|
| |
examples of use. These poke stuff not specifically targeted before, incl.
recursive local generators relying on nested scopes, ditto but also
inside class methods and rebinding instance vars, and anonymous
partially-evaluated generators (the N-Queens solver creates a different
column-generator for each row -- AFAIK this is my invention, and it's
really pretty <wink>). No problems, not even a new leak.
|
|
|
|
|
|
| |
"return expr" instances in generators (which latter may be generators
due to otherwise invisible "yield" stmts hiding in "if 0" blocks).
This was fun the first time, but this has gotten truly ugly now.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
that required explicitly calling LazyList.clear() in the two tests that
use LazyList (I added a LazyList Fibonacci generator too).
A real bitch: the extremely inefficient first version of the 2-3-5 test
*looked* like a slow leak on Win98SE, but it wasn't "really": it generated
so many results that the heap grew over 4Mb (tons of frames! the number
of frames grows exponentially in that test). Then Win98SE malloc() starts
fragmenting address space allocating more and more heaps, and the visible
memory use grew very slowly while the disk was thrashing like mad.
Printing fewer results (i.e., keeping the heap burden under 4Mb) made
that illusion vanish.
Looks like there's no hope for plugging the LazyList leaks automatically
short of adding frameobjects and genobjects to gc. OTOH, they're very
easy to break by hand, and they're the only *kind* of plausibly realistic
leaks I've been able to provoke.
Dilemma.
|
|
|
|
|
|
|
| |
Implement sys.maxunicode.
Explicitly wrap around upper/lower computations for wide Py_UNICODE.
When decoding large characters with UTF-8, represent expected test
results using the \U notation.
|
|
|
|
| |
not writable -- too dangerous!) from Python code.
|
|
|
|
|
| |
a non-dictionary mapping object. Include tests for several expected
failure modes.
|