Re: [Python-Dev] PEP 384 (stable api) question

2013-11-09 Thread Thomas Heller
Am 07.11.2013 19:35, schrieb "Martin v. Löwis": Am 07.11.13 13:44, schrieb Thomas Heller: I thought that the stable API would keep exactly the same across releases - is this expectation wrong or is this a bug? Oscar is right - this change doesn't affect the ABI, just the API. That said, plea

Re: [Python-Dev] PEP 384 (stable api) question

2013-11-07 Thread Nick Coghlan
On 8 Nov 2013 04:42, Martin v. Löwis wrote: > > Am 07.11.13 13:44, schrieb Thomas Heller: > > > I thought that the stable API would keep exactly the same across > > releases - is this expectation wrong or is this a bug? > > Oscar is right - this change doesn't affect the ABI, just the API. > > Tha

Re: [Python-Dev] PEP 384 (stable api) question

2013-11-07 Thread Martin v. Löwis
Am 07.11.13 13:44, schrieb Thomas Heller: > I thought that the stable API would keep exactly the same across > releases - is this expectation wrong or is this a bug? Oscar is right - this change doesn't affect the ABI, just the API. That said, please file an issue reporting what change you see i

Re: [Python-Dev] PEP 384 (stable api) question

2013-11-07 Thread Oscar Benjamin
On 7 November 2013 12:44, Thomas Heller wrote: > PEP 384 describes the stable Python api, available when > Py_LIMITED_API is defined. > > However, there are some (small) changes in the function prototypes > available, one example is (in Python 3.3): > PyObject* PyObject_CallFunction(PyObject *cal