When sending a Python integer as an argument to
PyLong_AsUnsignedLong, the following error occurs

SystemError: Objects/longobject.c:240: bad argument to
internal function

This error comes from the fact that
PyLong_AsUnsignedLong, unlike PyLong_AsLong, does not
check to see if the number is a long or integer, but
only a long.

This patch checks to see if the number is an integer,
and if so, calls PyInt_AsUnsignedLongMask.

Logged In: YES 
user_id=21627

Why is it desirable to accept ints in PyLong_AsUnsignedLong?

Logged In: YES 
user_id=350049

The reasons I submitted the patch:

* There's a precedent in the PyLong_AsLong code.
* The error was causing PyCDK (Python binding to the Curses
Development Kit) to segfault.
* Seeing as there's no data lost converting from int to
long, it makes sense to go ahead and convert instead of
crapping out.

Logged In: YES 
user_id=21627

I see. The precedent of PyLong_AsLong is a good rationale.
However, your patch is incorrect: It would return a value
for negative integers, whereas it should raise an
OverflowError in this case. I have committed a different
patch as longobject.c 1.165, NEWS 1.1138, which also adds
the same extension to PyLong_AsUnsignedLongMask.