Re: [Python-Dev] PyIndex_Check conflicts with PEP 384

2018-06-01 Thread Serhiy Storchaka
02.06.18 00:37, Christian Tismer пише: I was challenged end of last December to try that, and I succeeded after a long struggle, because I also needed to convert all of PySide2 to using heaptypes, and that was really hard. Actually, I succeeded yesterday, after 5 months. And now I know all the su

Re: [Python-Dev] PyIndex_Check conflicts with PEP 384

2018-06-01 Thread Christian Tismer
Hi Nate, I just did that, and I got some follow-up work, too, which is fine with me. Just as a note for you: Qt not itself, but PyQt5 did that already and submitted a stable ABI for Python 3.5 and up. I was challenged end of last December to try that, and I succeeded after a long struggle, becau

Re: [Python-Dev] PyIndex_Check conflicts with PEP 384

2018-06-01 Thread Nathaniel Smith
Indeed, that sounds like a pretty straightforward bug in the stable ABI. You should file an issue on bugs.python.org so it doesn't get lost (and if it's the main new stable ABI break in 3.7 then you should probably mark that bug as a release blocker so that Ned notices it). Unfortunately, very few

[Python-Dev] PyIndex_Check conflicts with PEP 384

2018-06-01 Thread Christian Tismer
Hi friends, when implementing the limited API for PySide2, I recognized a little bug where a function was replaced by a macro. The file number.rst on python 3.6 says """ .. c:function:: int PyIndex_Check(PyObject *o) Returns ``1`` if *o* is an index integer (has the nb_index slot of the t