Bryan belred1 at
Tue Jun 15 14:47:22 CEST 2004

Shankar KN wrote:
> Hi,
> Thanks for the reply.
> But the problem persists.
> There is only place where I do a #include <Python.h> (its in a .i file)
> I did what you suggested around this include.
> the problem is that running SWIG on this .i generates a .cxx file which we
> don't want to modify.
> This .cxx file has multiple occurences of #include <Python.h>, and only one
> occurence gets the "guard" against _DEBUG.
> Am I missing something here?

sorry, i don't use swig, so i'm no going be able to help you with that.  but couldn't you write a python post-process 
script that modifies the file automatically when compiled debug?  if this is too much of a pain, then maybe compiling a 
debug version of python would be your simplest solution.


More information about the Python-list mailing list