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.

pickle.py, where it makes save_newobj() unnecessary.  Tests pass.

used everywhere).

Use re module instead of regex

- subclasses of list or dict
- __reduce__ returning a 4-tuple or 5-tuple
- slots

   now crash because two arguments are expected.  Add a default value
   to keep those scripts running.

Fix use of GetoptError, so demo() now works

Backport candidate.

coverage.

   Simply replace all uses of statcache with os.stat.

Should I add a DeprecationWarning triggered if the use_statcache argument
is supplied, so we can remove it in 2.4?

Right now the test cases create a files and a directory in the temp.
directory.  Raymond suggested checking files in to the test/ directory,
simplifying the setup/teardown methods; is that worth doing?

Apparently MAC OS 9 doesn't have POSIX-conforming timestamps.  A test
fails as a result, but at least for this specific test it's easy enough
to get the POSIX epoch out of it.

http://mechanicalcat.net/cgi-bin/log/python/turning_warnings_off.html)