(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().

the tests will remain in sync:

"""
Tres discovered a weird bug when a datetime is pickled, caused by the
shadowing of __year, __month, __day and the use of proxies.

Here's a quick fix and a quick unit test.  I don't quite understand
why this wasn't caught by the pickling unit tests.
"""

Fix pydoc when doing help for:  and, or, not, UNICODE.

Will backport.

Make length an int so we get the right value from
PyArg_ParseTuple(args, "s#", &str, &length)

Will backport.

atomically, but deepcopy() didn't support this at all.
I don't see any reason for this, so I'm adding ClassType
to the set of types that are deep-copied atomically.

Rewrote copy() and deepcopy() without avoidable try/except statements;
getattr(x, name, None) or dict.get() are much faster than try/except.

eventProc (which simply drops all events on the floor). Also added a
method SetDefaultEventProc through which frameworks can set a global
event handler (which can still be overridden on a per-call basis
with the eventProc argument).

(Yes, this is an incompatibility.  I'll document it in PEP 307.)

  off-line readers
- fix some minor typos and markup errors

  too hard to read.
* Simplified previous changes to izip() to make it easier to read.

* Fixed typo in exception message for times()
* Filled in missing times_traverse()
* Document reasons that imap() did not adopt a None fill-in feature
* Document that count(sys.maxint) will wrap-around on overflow
* Add overflow test to islice()
* Check that starmap()'s argument returns a tuple
* Verify that imap()'s tuple re-use is safe
* Make a similar tuple re-use (with safety check) for izip()

Even with the extra work to cleanup the env, *BSD still leaks.  Add a note.

Will backport.

Closes SF bug #680797.

Reverting one of those irritating "security fixes".  fdopen() opens
files in binary mode.  That makes pydoc skip the \r\n on Windows that's
need to make the output readable in the shell.  Screw it.