Add \refs to GC section that were XXXed out.

Object/unicodeobject.c::unicode_count().

instead of PyTuple_GetItem, so an overwritten __getitem__
in a tuple subclass works. SF bug #665835.

- Allow for "manual:" pseudo-scheme in downloadURL to signal that
  the download should be done manually.

split into OPT and BASECFLAGS (Makefile.pre.in rev. 1.108), because
now there are essential CFLAGS in BASECFLAGS.

object is not a real str or unicode but an instance
of a subclass, construct the output via looping
over __getitem__. This guarantees that the result
is the same for function==None and function==lambda x:x

This doesn't happen for tuples, because filtertuple()
uses PyTuple_GetItem().

(This was discussed on SF bug #665835).

(preInstall, at least).

my MAL. Fixed. (Btw. eval() still doesn't take buffers, but that was so
even before my patch.)

Incorporated nnorwitz's comment re. Py__USING_UNICODE.

When subclassing from an int but not overriding __new__,
long values were not converted properly.  Try to convert
longs into an int.

Add Grant Olson for patch provided to fix bug #678518

less than 500 lines it already manages to test whether Numeric is installed,
and can install it if it isn't, including any prerequisites.

mark. Added unit test.

* Removed the ifilter flag wart by splitting it into two simpler functions.
* Fixed comment tabbing in C code.
* Factored module start-up code into a loop.

Documentation:
* Re-wrote introduction.
* Addede examples for quantifiers.
* Simplified python equivalent for islice().
* Documented split of ifilter().

Sets.py:
* Replace old ifilter() usage with new.

[ 678518 ] Another parsermodule validation error

tickle the 2.2.2 __cmp__ bug test_datetime used to tickle, so the
workarounds for that bug no longer make sense in the test suite (which I'm
still trying to keep as closely in synch as possible with Zope3's
version).

of datetime does, accept instances of subclasses too.

doesn't have UserDict.DictMixin.

__ne__ no longer complain if they don't know how to compare to the other
thing.  If no meaningful way to compare is known, saying "not equal" is
sensible.  This allows things like

    if adatetime in some_sequence:
and
    somedict[adatetime] = whatever

to work as expected even if some_sequence contains non-datetime objects,
or somedict non-datetime keys, because they only call __eq__.

It still complains (raises TypeError) for mixed-type comparisons in
contexts that require a total ordering, such as list.sort(), use as a
key in a BTree-based data structure, and cmp().