instantiating the class. Docs and tests are updated.

test_telnetlib.py with a basic test and timeout ones.
Docs are also updated.

the C lib's clock() is used, but it must be divided by CLOCKS_PER_SEC
as for the POSIX implementation (thanks to #pypy).

Consolidate patches #1690164, 1683397, and 1690169, all of which refactor XML-related test suites. The patches are applied together because they use a common output/xmltests file.
Thanks to Jerry Seutter for all three patches.

the test_smtplib.py file, with a basic test and the timeout
ones. Docs are updated too.

socket.recvfrom, which caused an ugly crash.

test_poplib.py file with a basic test and the timeout
ones. Docs are also updated.

the ftplib tests.

file to test the ftp lib (right now I included a basic test, the timeout
one, and nothing else).

for threading and socket serving.

regression tests.

Python 2.5 added support for explicit relative import statements and
yield expressions, which were missing in the manual.
Also fix grammar productions that used the names from the Grammar file,
markup that broke the generated grammar.txt, and wrap some lines that
broke the pdf output.  Will backport.

changes in the tests, so failing one test won't produce strange
results in others. Also relaxed the timeout settings in the test
(where actually the value didn't mean anything).

overflows the valid Py_ssize_t range.  Check return values of
PyMem_Malloc.

Will backport to release25-maint.

connection with an optional timeout, and modified httplib.py to
use this function in HTTPConnection. Applies patch 1676823.

type.__new__(), and then calls object.__init__(cls), just to be anal.

This allows us to restore the code in string.py's _TemplateMetaclass
that called super(...).__init__(name, bases, dct), which I commented
out yesterday since it broke due to the stricter argument checking
added to object.__init__().

Will backport.

Will backport.

  now stricter in rejecting excess arguments.  The only time when
  either allows excess arguments is when it is not overridden and the
  other one is.  For backwards compatibility, when both are
  overridden, it is a deprecation warning (for now; maybe a Py3k
  warning later).

When merging this into 3.0, the warnings should become errors.

Note: without the change to string.py, lots of spurious warnings happen.
What's going on there?

The code in this patch leaves no way to give up the ownership of a
BSTR instance.

now be unpickled. Will backport.