* Py_BuildValue("(OOO)",a,b,c)  -->  PyTuple_Pack(3,a,b,c)
* Py_BuildValue("()",a)         -->  PyTuple_New(0)
* Py_BuildValue("O", a)         -->  Py_INCREF(a)

useful for rapidly building argument tuples without having to invoke the
more sophisticated machinery of Py_BuildValue().

This should not be backported to 2.3, as it might break backwards
compatibility.

Make urlparse RFC 2396 compliant.
Closes bug #450225 (thanks Michael Stone).

Add Michael Stone for helping with bug #450225 (making urlparse RFC 2396
compliant).

(Contributed by Johannes Gijsbers.)

PyArg_ParseTuple() where possible.

Altered to return a PyBool instead of a PyInt.

Backport candidate.

classes

module existed in the current directory.  Fix this.  Backport
candidate (I presume).

change the version number is no longer required.

Instead, a make_versioninfo.exe is compiled, which spits out an
include file for python_nt.rc.

Will backport to 2.3

Backport candidate.

make obj.__contains__() returns True/False instead of 1/0.

Backported to 2.3

Not sure if this fix is great, but it's probably a small improvement.

Adopt Jeremy Fincher's suggested function name, "any", instead of "some".

* Added C coded getrandbits(k) method that runs in linear time.
* Call the new method from randrange() for ranges >= 2**53.
* Adds a warning for generators not defining getrandbits() whenever they
  have a call to randrange() with too large of a population.

SGI compiler and GCC seem to need this.

define _XOPEN_EXTENDED_SOURCE, the bug isn't triggered. Testing on
FreeBSD shows that nothing is broken by this change.

first line of a header section isn't an RFC-ish header, it's just
ignored instead of throwing an UnboundLocalError.

Backport candidate.

assuming it is the variable f.

Backported to 2.3.

  anonymous flavor unless the user asks for it on the command line
- decompose SourceForge authenticated CVS roots correctly

is None, the next row read is used as the fieldnames.  In the common case,
this means the programmer doesn't need to know the fieldnames ahead of time.
The first row of the file will be used.  In the uncommon case, this means
the programmer can set the reader's fieldnames attribute to None at any time
and have the next row read as the next set of fieldnames, so a csv file can
contain several "sections", each with different fieldnames.