[issue11587] METH_KEYWORDS alone gives "METH_OLDARGS is no longer supported!"

[Berker Peksag]

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 -> closed
superseder:  -> Error in Python 3 docs for PyMethodDef

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11587] METH_KEYWORDS alone gives "METH_OLDARGS is no longer supported!"

[Antti Haapala]

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 METH_KEYWORDS *cannot* be 
used without METH_VARARGS at all.

Furthermore, the default case should actually report the wrong flags value 
instead of calling it the "METH_OLDARGS", since it can be caused by any future 
combination, by setting it to zero, or undefined behaviour causing the flag to 
be overwritten.

--
nosy: +ztane

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11587] METH_KEYWORDS alone gives "METH_OLDARGS is no longer supported!"

[Jesse Ogle]

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

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11587] METH_KEYWORDS alone gives "METH_OLDARGS is no longer supported!"

[Clive Darke]

Clive Darke  added the comment:

Same error on 3.2 with Windows MSC v.1500 and Linux gcc version 4.1.2

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11587] METH_KEYWORDS alone gives "METH_OLDARGS is no longer supported!"

[Ray.Allen]

Ray.Allen  added the comment:

Looks like just the problem of error msg.

--
nosy: +ysj.ray

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11587] METH_KEYWORDS alone gives "METH_OLDARGS is no longer supported!"

[Clive Darke]

New submission from Clive Darke :

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, fails as described on 3.1.2 
and 3.2.

--
components: Extension Modules
messages: 131253
nosy: cdarke
priority: normal
severity: normal
status: open
title: METH_KEYWORDS alone gives "METH_OLDARGS is no longer supported!"
type: compile error
versions: Python 3.1, Python 3.2

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com