I attach a patch where I use PyArg_ParseTupleAndKeywords in socketmodule
where ARGSUSED was mentioned, or removed ARGSUSED if keywords already used.

What problem(s) does this solve?

It's not really for solving a problem, it's an enhancement to allow the
functions to be called with keyword parameters.

And what problem is solved by the removal of ARGSUSED?

For the functions whose signatures you changed, can you please add
documentation and test changes as well (where necessary)?

Please don't remove the arguments PyObject* on METHO_NOARGS functions;
that is incorrect.

Alright I'll add tests to the modified functions. I don't think I have
to change documentation because I kept the same name for the parameters,
but I'll check.

Looking at the patch more, maybe it doesn't make sense on the functions
taking only one parameter though :). I'll probably remove that.

Regarding ARGSUSED, I thought it was here to note functions using
PyArg_ParseTuple instead of PyArg_ParseTupleAndKeywords, but looking at
the svn history it seems wrong. I can put it back if there is another
semantic.

For METH_NOARGS, do you have a pointer to explain that?
http://docs.python.org/ext/node22.html, for example, show an example  of
METH_NOARGS with a function without arguments. Does that have other
incidence?

Here it is. There were several functions which didn't have any tests at
all, so I had to create some. These tests are likely to fail on some
platforms (like windows), but I didn't get any machine to test.

There's a new version, can we get it reviewed and tested under Windows?

Could someone please review these patches as they stand.  Will any rework of the patches be needed to get them into 3.2?

Could someone please review the latest patch, I'd like to see the OP's work rewarded with the patch getting into 3.2.

The patch needs updating for latest 3.x.