Move the clear to *before* the first use, not after.

4000 didn't work either.  1000 does work on Windows.  If 2000 works,
that will hopefully be a reasonable balance.

crashes on Windows are really due to the stack size or possibly
some other problem.

Windows and some other boxes.  If this is successful, this rev should
be backported.  I'm not sure how close to the limit we should push this.

accessing the message attribute instead of using the descriptor.

Python 2.5.

Also remove gopher support from urllib/urllib2.  As both imported gopherlib the
usage of the support would have raised a DeprecationWarning.

lack of an infinite recursion check.

Contributed by Damien Miller at Google.

Add what looks like a necessary call to PyErr_NoMemory() when PyMem_MALLOC()
fails.

Will backport.

the traceback inadvertently or maliciously closing the comment and
injecting HTML into the error page.

or earlier.  http://www.freebsd.org/releases/index.html

Hopefully Guido won't shed a tear. :-)

 (backport)

are zero.  This should help reduce the false positives.

The message about references leaking is maintained to provide as much
info as possible rather than simply suppressing the message at the source.

Fix a segfault when b"" was passed to b2a_qp() -- it was using strchr()
instead of memchr().

If the call to requires() doesn't precede the filesystem check, we get the following situation:
1. ./python Lib/test/regrtest.py test_foo # test needs urlfetch, not enabled, so skipped
2. ./python Lib/test/regrtest.py -u urlfetch test_foo # test runs
3. ./python Lib/test/regrtest.py test_foo # test runs (!)

By moving the call to requires() *before* the filesystem check, the fact that fetched files are cached on the local disk becomes an implementation detail, rather than a semantics-changing point of note.