> 3. A crazy idea is to arrange to port the modules to managed C++
> combined with a fake set of include files that makes the
> modules really
> link with IronPython rather than CPython. In theory, this
> could let the
> modules work well with IronPython with only a recompile required. This
> cou
Timothy Fitz wrote:
> Where there be any plans for allowing IronPython to work with an
> instance of CPython directly? There are quite a few instances where
> this would be extremely handy (SWIG-wrapped libraries such as
> wxPython, or tightly optimized pieces that deal directly with
> operating sy
Where there be any plans for allowing IronPython to work with an
instance of CPython directly? There are quite a few instances where
this would be extremely handy (SWIG-wrapped libraries such as
wxPython, or tightly optimized pieces that deal directly with
operating system concepts such as Twisted
