Stelios Xanthakis wrote: > There are two kinds of C modules: those that do have a knowledge > of the C API (like sre, tkinter, etc) and those that are just C/C++ > libraries which are simply wrapped as modules. For the latter there > are two solutions besides adding a wrapper which makes pyvm appear > as libpython: > - an advanced ctypes module which will make dlopening libraries > and wrapping their symbols behind python functions, a matter of > python code. I'm considering this approach to provide things > like 'raw_input'. > - hacking SWIG. Shouldn't be too hard and will instantly give > us access to wx, qt, etc.
No, writing a pyvm modules for SWIG won't give you compatibility with most existing SWIG wrappers. Such wrappers are very, very rarely "pure SWIG". Almost all nontrivial wrappers include ad hoc typemaps that use the Python C API. -- Robert Kern [EMAIL PROTECTED] "In the fields of hell where the grass grows high Are the graves of dreams allowed to die." -- Richard Harter -- http://mail.python.org/mailman/listinfo/python-list
