usually preferred.

When parsing the constructor arguments failed, a
reference to the argument tuple was leaked.

when an encoding error occurs and the callback name is unknown,
i.e. when the callback has to be called. The problem was that
the fact that the callback has already been looked up was only
recorded in a local variable in charmap_encoding_error(), because
charmap_encoding_error() got it's own copy of the errorHandler
pointer instead of a pointer to the pointer in
PyUnicode_EncodeCharmap().

(Contributed by George Yoshida.)

Check for a[:] = a _before_ calling PySequence_Fast on a.
release23-maint candidate
Reference leak doesn't happen with head of release22-maint.

the output was consumed would cause and exception to be raise in
logmerge; suppress this specific error, because it's not helpful.

on W2K and XP.  Python Bugs 780451, 784183

Backported to 2.2-maint

UnicodeTranslateError message.

If there is only one bad character it will now be printed in a
form that is a valid Python string.

Now test_descr only appears to leak two references & I think this
are in fact illusory (it's to do with things getting resurrected in
__del__ methods & it's easy to be believe confusion occurs when that
happens <wink>).  Woohoo!

docs

the tp_name is not correct, but what's exposed to users is known visibly as
"StringIO", not "StringI" or "StringO".

This should go onto release23-maint, too.

under Cygwin. The attached patch corrects this problem.

I tested this patch under Red Hat Linux 8.0 too.

but attempting to get it resulted in a crash. Fixed. Backport candidate.

time.daylight is true.  Add an explicit test for this situation.

Fixed some wording in docstrings.

The default seed is time.time().
Multiplied by 256 before truncating so that fractional seconds are used.
This way, two successive calls to random.seed() are much more likely
to produce different sequences.

Verify that the encoding actually exists. Fixes #775985.
Will backport to 2.3.

(Contributed by Andrew Dalke.)

(Contributed by Jay T Miller.)

backported to 23-maint

Sure looks like it to me! <wink>

When I run the leak2.py script I posted to python-dev, I only see
three reference leaks in all of test_descr.  When I run
test_descr.test_main, I still see 46 leaks.  This clearly demands
posting a yelp to python-dev :-)

This certainly should be applied to release23-maint, and in all
likelyhood release22-maint as well.

which can now take zero arguments.