[IronPython] How to use IronPython to generate DLLs consumablebyother .NET modules?

Keith J. Farmer kfarmer at thuban.org
Tue Aug 16 01:39:36 CEST 2005


By calling "C", you mean calling "CPython bytecode", right, since Python only calls C by virtue of having stubs available (eg, such as those produced by SWIG).  IronPython could have these even more directly, I think (via DllImport, and no need for SWIG)
 
As far as CPython bytecode, someone could probably make a Python bytecode to IL translator, once IronPython starts saving assemblies.

________________________________

From: users-ironpython.com-bounces at lists.ironpython.com on behalf of Michael Gogins
Sent: Sat 8/13/2005 2:26 PM
To: Discussion of IronPython
Subject: Re: [IronPython] How to use IronPython to generate DLLs consumablebyother .NET modules?


IronPython implements Python in C#, and can call .NET  but not C.
PythonNet implements Python in C, and can call both .NET and C.
 
IronPython is probably the closest to what you want, since Python classes should also be .NET classes.
 



More information about the Ironpython-users mailing list