| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Backported to 2.4.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
examples no longer require any explicit closing to avoid
leaking.
That the tee-based examples still do is (I think) still a
mystery. Part of the mystery is that gc.garbage remains
empty: if it were the case that some generator in a trash
cycle said it needed finalization, suppressing collection
of that cycle, that generator _would_ show up in gc.garbage.
So this is acting more like, e.g., some tp_traverse slot
isn't visiting all the pointers it should (in which case
the skipped pointer(s) would act like an external root,
silently suppressing collection of everything reachable
from it(them)).
|
|
|
|
|
|
|
|
|
|
|
| |
problems: first, PyGen_NeedsFinalizing() had an off-by-one bug that
prevented it from ever saying a generator didn't need finalizing, and
second, frame objects cleared themselves in a way that caused their
owning generator to think they were still executable, causing a double
deallocation of objects on the value stack if there was still a loop
on the block stack. This revision also removes some unnecessary
close() operations from test_generators that are now appropriately
handled by the cycle collector.
|
| |
|
|
|
|
|
|
|
|
|
| |
an incremental encoder that must retain part of the data between calls
to the encode() method.
Fix the incremental encoder and decoder for the IDNA encoding.
This closes SF patch #1453235.
|
| |
|
| |
|
| |
|
|
|
|
| |
uncommon but possible. Inspired by SF bug 1469629.
|
|
|
|
| |
incremental codec tests.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The test case came from test_generators, not test_itertools.
Ensure there's no cyclic garbage we are counting.
This is weird because it leaks, then reaches a limit:
python.exe -i test_tee.py
>>> leak()
0
[26633 refs]
>>> leak()
0
[26658 refs]
>>> leak()
0
[26683 refs]
>>> leak()
0
[26708 refs]
>>> leak()
0
[26708 refs]
>>> leak()
0
[26708 refs]
>>> leak()
0
|
| |
|
|
|
|
| |
fixed.
|
|
|
|
|
|
|
| |
appear. Get rid of them by nuking doctest's default DocTestRunner
instance as part of cleanup(). Also cleanup() before running the
first test repetition (the test was run once before we get into
the -R branch).
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
This may be causing the debian sparc buildbot to fail.
Print a little message to let the user ^w buildbot know it's still thinking.
We may want to adjust the time period which is currently 5 minutes.
Will backport.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
prepends the exception's module name to non-builtin exceptions, like
the interpreter itself does.
broke a number of doctests. should be discussed before checking in (see
discussion on python-dev).
|
|
|
|
|
| |
exception's module name to non-builtin exceptions, like the interpreter
itself does.
|
|
|
|
|
|
|
|
|
| |
bsddb.*open() methods cachesize parameter wouldn't work (raised an
internal bsddb.db exception when it was given). The set_cachesize
call needed to be moved from the DB object to the DBEnv since the env
was introduced to allow for threading.
(will backport to 2.4)
|
|
|
|
|
|
|
| |
Using None for a filename with the 'n' flag when calling bsddb.btopen
would cause an error while checking if the file None existed. error
not likely to be seen as anyone using None for a filename would likely
use the 'c' flag in the first place.
|
|
|
|
| |
https://sourceforge.net/tracker/?func=detail&atid=532154&aid=1467852&group_id=71702
|
|
|
|
| |
Font.__del__ is run.
|
|
|
|
| |
e.g. SimpleXMLRPCServer wasn't in here yet.
|
|
|
|
| |
Wrapped in a try/except.
|
|
|
|
| |
Add tests for the output of the TextCalendar and HTMLCalendar classes.
|
|
|
|
| |
Add tests for generator expressions too.
|
|
|
|
| |
for the bogus failure.
|
|
|
|
| |
stream (see SF bug #1463840).
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
"x86 OpenBSD trunk" buildbot due to changing Python so that
Python-exposed addresses are always non-negative.
test_int_pointer_arg(): This line failed now whenever the
box happened to assign an address to `ci` "with the sign
bit set":
self.failUnlessEqual(addressof(ci), func(byref(ci)))
The problem is that the ctypes addressof() inherited "all
addresses are non-negative now" from changes to
PyLong_FromVoidPtr(), but byref() did not inherit that
change and can still return a negative int.
I don't know whether, or what, the ctypes implementation wants
to do about that (possibly nothing), but in the meantime
the test fails frequently.
So, introduced a Python positive_address() function in
the test module, that takes a purported machine address and,
if negative, converts it to a non-negative value "with the
same bits". This should leave the test passing under all
versions of Python.
Belated thanks to Armin Rigo for teaching me the sick trick ;-)
for determining the # of bits in a machine pointer via abuse
of the struct module.
|
|
|
|
|
|
|
| |
tests. Alas, because only the "x86 OpenBSD trunk" buildbot fails
these tests, and test_descr stops after the first failure, there's
no sane way for me to fix these short of fixing one and then
waiting for the buildbot to reveal the next one.
|
| |
|
|
|
|
|
|
| |
test. Add some lines that at least invoke the default
__hash__, although there's nothing to check there beyond
that they don't blow up.
|
|
|
|
|
| |
to work correctly with modules imported from zipfiles or via other PEP 302
__loader__ objects. Tests and doc updates are included.
|
|
|
|
| |
didn't commit it.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to that id() can now return a Python long on a 32-bit box that allocates
addresses "with the sign bit set".
test_set.py test_subclass_with_custom_hash(): it's never been portably
legal for a __hash__() method to return id(self), but on 32-bit boxes
that never caused a problem before it became possible for id() to
return a Python long. Changed __hash__ here to return a Python int
regardless of platform.
test_descr.py specials():
vereq(hash(c1), id(c1))
has never been a correct test -- just removed it (hash() is always
a Python int; id() may be a Python long).
|
|
|
|
|
| |
due to that id() may return a long on a 32-bit box now. On a box that
assigns addresses "with the sign bit set", id() always returns a long now.
|
|
|
|
|
| |
to that id() may return a long on a 32-bit box now. On a box that assigns
addresses "with the sign bit set", id() always returns a long now.
|
| |
|
|
|
|
|
|
| |
default decimal context, causing test_tokenize to fail
if it ran after test_contextlib. Changed to restore
the decimal context in effect at the test's start.
|
|
|
|
| |
it was being run, but no tests were actually executed!
|
| |
|
|
|
|
|
|
| |
Introduce _child_active member to keep track on whether a child
needs to be waited for.
Backport candidate.
|
|
|
|
| |
--enable-shared. Fixes #832799.
|
| |
|