[issue10681] PySlice_GetIndices() signature changed

Dave Malcolm 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://bugzill

[issue10681] PySlice_GetIndices() signature changed

Martin v. Löwis 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

[issue10681] PySlice_GetIndices() signature changed

Phil Thompson added the comment: It's source level incompatible - my extension modules compiled fine with v3.2a but failed with v3.2b1. -- ___ Python tracker ___ __

[issue10681] PySlice_GetIndices() signature changed

Martin v. Löwis added the comment: It's not an incompatible change, but I added the versionchanged anyway in r87173. -- ___ Python tracker ___ _

[issue10681] PySlice_GetIndices() signature changed

Phil Thompson added the comment: You might want to add a "Changed in Python v3.2" because as it is an incompatible change. -- ___ Python tracker ___ ___

[issue10681] PySlice_GetIndices() signature changed

Martin v. Löwis added the comment: The source is correct. Fixed in r87171. -- nosy: +loewis resolution: -> fixed status: open -> closed ___ Python tracker ___ _

[issue10681] PySlice_GetIndices() signature changed

New submission from Phil Thompson : 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?