<loewis@informatik.hu-berlin.de>.

Reorganized to be more like other parts of the documentation in its
arrangement, but with few content changes.

This closes SourceForge patch #101850.

msg/headers are empty and the entire response is treated as the body.

This should close SF bug (patch)
http://sourceforge.net/patch/?func=detailpatch&patch_id=101844&group_id=5470

    - don't close the fp, since that appears to also close the socket
    - join the original url with the redirect reponse to deal with
      relative redirect URL

wrap two socket ops in try/except to turn them into URLErrors, so that
client code need only catch one exception.

in HTTPError.__del__ only close fp if fp is not None

style changes:
    - use f(*args) instead of apply(f, args)
    - use __super_init instead of super.__init__(self, ...)

use standard Python style for whitespace near = and ()

Direct use of interp->result is deprecated; changing this to
Tcl_GetStringResult(interp) everywhere fixed the problem of losing the
error message with TclError exceptions, on Windows.

-Wstrict-prototypes options.  This will make it a lot easier to keep
warnings under control in the first place in the future.

There is one known warning at this time, caught by the -Wstrict-prototypes
option.  In Modules/main.c, the declaration of getopt() without parameters
gets a complaint (rightly) that it is not a proper prototype.  The lack of
a complete prototype information should be corrected when the right
portability conditions have been identified.

Approved by the Guido.

http://sourceforge.net/bugs/?func=detailbug&bug_id=116636&group_id=5470
bobalex@rsv.ricoh.com

Bug report: If the file position is less than the end of the "file",
and a write is performed extending past then end of the file, the data
string is corrupted.

Solution: in write(), when writing past the end, properly set self.len
when newpos is > self.len.

Let's hope this is correct (I'm not sure why the sys.platform would be
'Darwin1.2' rather than 'darwin1', which seems to be the convention).

Someone with Darwin please test this!

changes.  Here restoring them.

libm result is 0).  Cautiously add a few libm exception test cases:
1. That exp(-huge) returns 0 without exception.
2. That exp(+huge) triggers OverflowError.
3. That sqrt(-1) raises ValueError specifically (apparently under glibc linked
   with -lieee, it was raising OverflowError due to an accident of the way
   mathmodule.c's CHECK() macro happened to deal with Infs and NaNs under gcc).

and it would look kind of silly if typeset.

   left that wasn't covered.  The article is therefore now essentially complete.)
A few minor changes

assuming here that the ANSI-C adjacent-string-concatenation technique is
allowable, now that Python requires an ANSI C compiler.

Py_FatalError() instead, and clarify the message somewhat. As discussed on
python-dev.

Moved appendChild calls from DOMEventStream to PullDOM (parser indep).
Removed duplicated sibling pointer setting (duplicated in appendChild).

support for extension types, not classes.

pickle():  If the type is a class or if the reduction function is not
           callable, raise a TypeError.

constructor():  If the constructor is not callable, raise TypeError.

This (partially) closes SourceForge patch #101859.

MPZ_divm():  Initialize mpzden to NULL, since it could be Py_XDECREF()ed
             without being initialized.

string.letters was much more than expected.

Solution: explicit is better than implicit; don't rely on
string.letters.

a bug in JPython where the instance had to have a flush() method.

groupings are still maintained.  Based on a comment by Steve Holden
<sholden@holdenweb.com>.

on Win64.

This closes bug http://sourceforge.net/bugs/?func=detailbug&group_id=5470&bug_id=116516

variable.  w should be initialized before entering the bytecode
interpretation loop since we only need one initialization to satisfy the
compiler.

by making the DUP_TOPX code utterly straightforward.  This also gets rid
of all normal-case internal DUP_TOPX if/branches, and allows replacing one
POP() with TOP() in each case, so is a good idea regardless.

Based on a comment from Detlef Lannert
<lannert@lannert.rz.uni-duesseldorf.de>.

<lannert@lannert.rz.uni-duesseldorf.de>.

these computations are required for their side effects in traversing the
variable arguments list.

Reported by Marc-Andre Lemburg <mal@lemburg.com>.

than the built-in string types (suggested by Moshe Zadka
<moshez@math.huji.ac.il>).

Clarified what "can be converted to a string" means.

Fixed a few markup nits.

one comment in the example for clarity.

Yee <ping@lfw.org> and probably others as well.