Message42177
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. |
|
Date |
User |
Action |
Args |
2007-08-23 15:19:22 | admin | link | issue660559 messages |
2007-08-23 15:19:22 | admin | create | |
|