when a parse node grows a very large number of children.  This sidesteps
platform realloc() disasters on several platforms.

Closes SF bug #578420.

Clarify the return value when the parameter is a Unicode object.

attributes of the TestResult.

TestResult object.  Add an example of how to get even more information for
apps that can use it.
Closes SF bug #558278.

The 2.2 maintenace branch is now identical to the trunk through rev
1.53.

2.2.1 has another bug that prevents the regression (which isn't a
regression at all) from showing up.  "The regression" is actually a
glitch in cyclic gc that's been there forever.

As the generation being collected is analyzed, objects that can't be
collected (because, e.g., we find they're externally referenced, or
are in an unreachable cycle but have a __del__ method) are moved out
of the list of candidates.  A tricksy scheme uses negative values of
gc_refs to mark such objects as being moved.  However, the exact
negative value set at the start may become "more negative" over time
for objects not in the generation being collected, and the scheme was
checking for an exact match on the negative value originally assigned.
As a result, objects in generations older than the one being collected
could get scanned too, and yanked back into a younger generation.  Doing
so doesn't lead to an error, but doesn't do any good, and can burn an
unbounded amount of time doing useless work.

A test case is simple (thanks to Kevin Jacobs for finding it!):

x = []
for i in xrange(200000):
    x.append((1,))

Without the patch, this ends up scanning all of x on every gen0 collection,
scans all of x twice on every gen1 collection, and x gets yanked back into
gen1 on every gen0 collection.  With the patch, once x gets to gen2, it's
never scanned again until another gen2 collection, and stays in gen2.

Opened another bug about that 2.2.1 isn't actually tracking (at least)
iterators, generators, and bound method objects, due to using the 2.1
gc API internally in those places (which #defines itself out of existence
in 2.2.x).

Closes SF bug #575272.

Backport 1.37: dis.dis() also supports modules, (also backport other changes back to 1.33 since these all apply to 2.2)

Add more links to the "See also" section for the xml.sax package.
Talk about interfaces rather than implementation classes where appropriate.
Add hyperlinks to make the documentation on the Attributes and AttributesNS
interfaces more discoverable.
Closes SF bug #484603.

and examples of the dict() constructor.

Fix typo.

Closes SF bug #572169.

Typo fix.

PyUnicode_Find().
This closes SF bug #566631.

Closes SF bug #571759.

(which makes it more clear).
Closes SF bug #571767.

(Hanging around small kids too much...;)

hints about how to work around it.
Closes SF bug #530637.

when used as part of the import statement.

Note that both "as" and "None" becoming keywords in the future.

Closes SF bug #553262.

Closes SF bug #551912.

Patch from SF bug 570483 (Tim Northover).

In a fresh interpreter, type.mro(tuple) would segfault, because
PyType_Ready() isn't called for tuple yet.  To fix, call
PyType_Ready(type) if type->tp_dict is NULL.

Based on patch contributed by Sean Reifschneider.
Closes SF patch #570618.

This closes SF patch #569832.

Closes SF bug #556370.