Speed-up calls and tighten code in operator.c 
arraymodule.c, and cStringIO.c by using METH_O, 
METH_NOARGS and PyArg_UnpackTuple.

Didn't touch other modules that I wasn't familiar with 
or that didn't look like they would benefit from the 
speedup.

Logged In: YES 
user_id=31435

Note that a METH_NOARGS function is still called, at the C 
level, with two arguments.  The second argument is always 
NULL, and sooner or later some platform C is going to blow 
up when that's passed to a function declared to take only 
one argument ("the usual" cast to PyCFunction shuts up the 
compile-time warnings).

It's not your job to fix that everywhere, but new uses of 
METH_NOARGS shouldn't add to this problem.  Declaring a 
second PyObject * argument with a name like "unused" 
or "dummy" would be fine.

Logged In: YES 
user_id=80475

Fixed.  Revised patch attached.

Logged In: YES 
user_id=357491

So I just finished reading the diff and it all looks good to
me (I think).  I basically just read through the diff and
when I saw  the original I tried to guess how Raymond
changed it and see what he did, in fact, change it to in the
end.  All turned out the way I expected it.

Logged In: YES 
user_id=21627

I agree that the patch looks fine; Raymond, please apply it.

Logged In: YES 
user_id=80475

Checked in as: arraymodule.c 2.80, cStringIO.c 2.39,and 
operator.c 2.26.

Thank you Tim, Brett, and Martin for the quality control.