This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Joshua.J.Cogliati
Recipients Joshua.J.Cogliati, ciantic, eric.araujo, lemburg, pebbe, tarek
Date 2014-11-05.22:10:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The documentation does claim that swig should just work "the build_ext command knows how to deal with SWIG extensions: it will run SWIG on the interface file and compile the resulting C/C++ file into your extension."

It would be nice if there was one obvious way to compile a swig extension.  (See for example the workarounds suggested in )
Date User Action Args
2014-11-05 22:10:12Joshua.J.Cogliatisetrecipients: + Joshua.J.Cogliati, lemburg, tarek, eric.araujo, ciantic, pebbe
2014-11-05 22:10:12Joshua.J.Cogliatisetmessageid: <>
2014-11-05 22:10:12Joshua.J.Cogliatilinkissue7562 messages
2014-11-05 22:10:12Joshua.J.Cogliaticreate