Martin v. Löwis added the comment:
I agree with Serhiy. This use case is not supported, i.e. it getting this
compiler warning if you implement a function from the interpreter core is not a
bug.
The work-around that he suggests sounds reasonable to me.
--
nosy: +loewis
resolution: -
Serhiy Storchaka added the comment:
I think this change doesn't break ABI and doesn't break applications which use
PyObject_CallFunction() in usual way. The only problem with your application is
compiler warning.
To silence a warning you can do:
#if PY_VERSION_HEX = 0x0304
# define
New submission from Thomas Heller:
(As requested by email in python-dev I'm reporting this problem)
Some function prototypes in the stable ABI have been changed between Python 3.3
and 3.4.
PyObject_CallFunction is an example, the second parameter has been changed from
'char *' to 'const char
Ezio Melotti added the comment:
See #9369 and #1772673.
--
nosy: +ezio.melotti, serhiy.storchaka
type: - behavior
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19538
___
Changes by STINNER Victor victor.stin...@gmail.com:
--
nosy: +haypo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19538
___
___
Python-bugs-list
