[IronPython] v1.1 IronPython.CodeDom.PythonProvider
dinov at microsoft.com
Mon Nov 30 20:16:19 CET 2009
Just to comment on this - pyc has always behaved quite differently then how the CodeDom compilation support worked. The CodeCom compilation support in particular was a hack so that we could support ASP.NET as it usually behaves. It was also fairly buggy and we didn't bring it forward to 2.6. The big difference between the two is that pyc produces code which IronPython can load while CodeDom produced a .NET assembly with specific types declared in specific namespaces based upon how the code was laid out. You could then load this assembly and instantiate those types and they'd still behave like Python types.
If we brought this back I think we'd want to do a better job on it then we did in 1.x and it'd be a fair amount of work. Feel free to file a feature request on CodePlex and have people vote on it if there's general interest in seeing it again.
From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of Aravin
Sent: Wednesday, November 25, 2009 8:37 PM
To: 'Discussion of IronPython'
Subject: Re: [IronPython] v1.1 IronPython.CodeDom.PythonProvider
As far as I know if you want to compile a python code you could use: clr.CompileModules(...). Or you could use the pyc.py provided in the IronPython2.0 Samples download.
ipy.exe pyc.py /main:winforms_hw.py /target:winexe which will produce a winforms_hw.dll as well. I'm not sure if you could use these compiles assemblies from C# or VB but with Ironpython it should be possible. I'm not sure if this is what you were looking for but hope it helps.
From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of Owen Sigurdson
Sent: Wednesday, November 25, 2009 11:23 PM
To: users at lists.ironpython.com
Subject: [IronPython] v1.1 IronPython.CodeDom.PythonProvider
I am attempting to upgrade a component from iron python 1.1 to 2.6 that was previously using the PythonProvider to compile python code into a .NET assembly. It looks like this is no longer present in 2.6. Is this correct? Are their any plans to resurrect it? The biggest difficulty I am facing is not that we require the code to be compiled in an assembly but that reflection used to return methods in an python class. Now reflecting on a python class (that subclasses a given .NET class) only returns the .NET class members.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ironpython-users