[issue10681] PySlice_GetIndices() signature changed
New submission from Phil Thompson <phil@riverbankcomputing.com>: In Python v3.2b1 the type of the first argument of PySlice_GetIndices() and PySlice_GetIndicesEx() has changed from PySliceObject* to PyObject*. The documentation does not reflect this change. Which is correct, the source code or the documentation? ---------- assignee: docs@python components: Documentation, Interpreter Core messages: 123809 nosy: Phil.Thompson, docs@python priority: normal severity: normal status: open title: PySlice_GetIndices() signature changed type: behavior versions: Python 3.2 _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue10681> _______________________________________
Martin v. Löwis <martin@v.loewis.de> added the comment: The source is correct. Fixed in r87171. ---------- nosy: +loewis resolution: -> fixed status: open -> closed _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue10681> _______________________________________
Phil Thompson <phil@riverbankcomputing.com> added the comment: You might want to add a "Changed in Python v3.2" because as it is an incompatible change. ---------- _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue10681> _______________________________________
Martin v. Löwis <martin@v.loewis.de> added the comment: It's not an incompatible change, but I added the versionchanged anyway in r87173. ---------- _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue10681> _______________________________________
Phil Thompson <phil@riverbankcomputing.com> added the comment: It's source level incompatible - my extension modules compiled fine with v3.2a but failed with v3.2b1. ---------- _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue10681> _______________________________________
Martin v. Löwis <martin@v.loewis.de> added the comment:
It's source level incompatible - my extension modules compiled fine with v3.2a but failed with v3.2b1.
That's because you are using C++, right? In C, there shouldn't be any problems. ---------- _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue10681> _______________________________________
Dave Malcolm <dmalcolm@redhat.com> added the comment: For reference, this seems to affect SWIG, specifically, I'm seeing build failures using: /usr/share/swig/2.0.1/python/pycontainer.swg from swig-2.0.1 See downstream build failure report for znc, which uses swig to generate python 3 bindings: https://bugzilla.redhat.com/show_bug.cgi?id=666429 ---------- nosy: +dmalcolm _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue10681> _______________________________________
participants (3)
-
Dave Malcolm -
Martin v. Löwis
-
Phil Thompson