Berker Peksag added the comment:
issue 15657 is actually a duplicate of this issue, but since there's more
information there I'm closing this. Please take a look the patch at issue
15657. Thank you all!
--
nosy: +berker.peksag
resolution: - duplicate
stage: - resolved
status: open -
Antti Haapala added the comment:
This is *still* there in Hg tip: PyCFunction_Call in Objects/methodobject.c
does not have a case for `METH_KEYWORDS` only at all.
The documentation for METH_KEYWORDS says that it is *typically* coupled with
METH_VARARGS; however not having the case means that
Jesse Ogle added the comment:
Same error with Python 3.3.1
Objects/methodobject.c: PyCFunction_Call()
Switch contains case for METH_VARARGS | METH_KEYWORDS but not
METH_KEYWORDS. I assume this is on purpose?
--
nosy: +jogle
versions: +Python 3.3
New submission from Clive Darke clive.da...@qa.com:
In the PyMethodDef struct, METH_VARARGS | METH_KEYWORDS works fine.
METH_KEYWORDS on its own gives:
SystemError: Bad call flags in PyCFunction_Call. METH_OLDARGS is no longer
supported!
METH_KEYWORDS on its own tested OK on 2.6 and 2.7,
Ray.Allen ysj@gmail.com added the comment:
Looks like just the problem of error msg.
--
nosy: +ysj.ray
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11587
___
Clive Darke clive.da...@qa.com added the comment:
Same error on 3.2 with Windows MSC v.1500 and Linux gcc version 4.1.2
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11587
___
