The C-code in fileobject.readinto(buffer) which parses
    the arguments assumes that size_t is interchangeable
    with int:

	    size_t ntodo, ndone, nnow;

	    if (f->f_fp == NULL)
		    return err_closed();
	    if (!PyArg_Parse(args, "w#", &ptr, &ntodo))
		    return NULL;

    This causes a problem on Alpha / Tru64 / OSF1 v5.1
    where size_t is a long and sizeof(long) != sizeof(int).

    The patch I'm proposing declares ntodo as an int.  An
    alternative might be to redefine w# to expect size_t.

[We can't change w# because there are probably third party modules
relying on it. GvR]

PyArg_UnpackTuple() function (serves as an example and test case).

    Fulton, based on code Jim supplied.

Make convertbuffer() static like the prototype says.  Not used elsewhere.

Repair unlikely surprise due to magical softspace attr and the use of
print with a trailing comma in doctest examples.
Bugfix candidate.

functions.

This should eliminate the traceback returned by sys.exc_info() as a
common source of memory leaks.

used by the weakref code since he didn't like the word "referencable".
Is it really necessary to be more specific than to test for TypeError here,
though?

template string, and don't call the template compiler if we can
avoid it.

failobj has to be a list or the `+' can fail.

    Don't put paren in column 0 (to please font-lock mode).
    Put space after comma in argument list.

    the curses module.  It's not run automatically; '-u curses' must be
    specified as an argument to regrtest

Mozilla 0.9.5 can make intelligent use of them.  Specifically, this causes
the "Acknowledgements" and "Global Module Index" pages to acquire "up"
links in the Mozilla "Site Navigation Bar".
This partially responds to SF bug #469772.

differences by defining symbols not defined on particular platforms.
This closes SF bug #473433.

\filename{} should be \file{}

(sorry, barry)

response to a message by Laura Creighton on c.l.py.  E.g.

    >>> 0+''
    TypeError: unsupported operand types for +: 'int' and 'str'

(previously this did not mention the operand types)

    >>> ''+0
    TypeError: cannot concatenate 'str' and 'int' objects

There really isn't a good reason for instance method objects to have
their own __dict__, __doc__ and __name__ properties that just delegate
the request to the function (callable); the default attribute behavior
already does this.

The test suite had to be fixed because the error changes from
TypeError to AttributeError.

(formerly these were silently ignored).  The only built-in methods
that take keyword arguments are __call__, __init__ and __new__.

checking in changes.  The test suite requires consistent use of spaces
and tabs.)

This fixes SF bug: [ #473491 ] "install -d" doesn't work on HP-UX.