[issue5431] cmpfunc in Python 3.0.1 windows installer

Terry J. Reedy added the comment: This development issues tracker is for issues that might result in changes in future Python releases. This issue was properly closed and in the absence of a new proposal for future change, should have stayed closed, even with the addition of a comment. The onl

[issue5431] cmpfunc in Python 3.0.1 windows installer

Nigel Galloway added the comment: Not quite an answer to the question. I have built this wrapper with the change to Python indicated. It seems to work. It does not complain about unresolved references. Is this satisfactory for 3.0.1, with perhaps a change to SWIG from 3.1. Or must I obtain Py

[issue5431] cmpfunc in Python 3.0.1 windows installer

Martin v. Löwis added the comment: > I'm sure swig was ported to python 3.0. > Is 3.0.1 allowed to break code developed with 3.0? Of course it was! Removal of cmp support was a deliberate breakage made in 3.0.1, see issue1717. In any case, it isn't coming back.

[issue5431] cmpfunc in Python 3.0.1 windows installer

Amaury Forgeot d'Arc added the comment: I'm sure swig was ported to python 3.0. Is 3.0.1 allowed to break code developed with 3.0? http://svn.python.org/view/python/branches/release30-maint/Include/object.h?r1=69215&r2=69221 -- nosy: +amaury.forgeotdarc ___

[issue5431] cmpfunc in Python 3.0.1 windows installer

Martin v. Löwis added the comment: This is not a bug in Python; apparently, SWIG hasn't been ported to Python 3.0.1. -- nosy: +loewis resolution: -> invalid status: open -> closed ___ Python tracker __

[issue5431] cmpfunc in Python 3.0.1 windows installer

New submission from Nigel Galloway : C:\Users\Nigel\myPython\iajaar>C:\Users\Nigel\swigwin-1.3.38\swig - c++ -python -py3 NigelzGLPK.swg generated a C++ wrapper and a Python file. When I attempted to compile the wrapper against Python 3.0.1 it failed see the output log at the end of this mess