<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7623.0">
<TITLE>RE: [IronPython] IronPython 0.9 released</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>As for the static compilation, it is another 'maybe' for 1.0 and we are not decided one way or another (it is another topic you can provide feedback on and let us know how important it is to you).</FONT></P>
<P><FONT SIZE=2>For the 0.9 I actually went somewhat further with the static compilation story and made the whole test suite to run from the compiled exes. Surely, it is not the answer to the 'static compilation' problem, but in the least somewhat more complicated scripts (i.e. those that used import) can run in some cases. So the story is slowly getting better already, but it still has a long way to go to be perfect and we are trying to determine the importance for our users to help use choose whether to try and implement it for 1.0 or later.</FONT></P>
<P><FONT SIZE=2>Martin</FONT>
</P>
<P><FONT SIZE=2>________________________________________</FONT>
<BR><FONT SIZE=2>From: Keith J. Farmer</FONT>
<BR><FONT SIZE=2>Sent: 8/4/2005 3:11 AM</FONT>
<BR><FONT SIZE=2>To: Discussion of IronPython</FONT>
<BR><FONT SIZE=2>Cc:</FONT>
<BR><FONT SIZE=2>Subject: RE: [IronPython] IronPython 0.9 released</FONT>
</P>
<P><FONT SIZE=2>I'm not sure where you got the idea that IronPython 1.0 only works with .NET 1.1?</FONT>
<BR><FONT SIZE=2>I can compile the IronPython solution using the VS 2005 Beta 2 release (and have, several times tonight). For what it's worth, IronPython needs the 2.0 runtime, since it uses 2.0 code generation, and supports 2.0 generics.</FONT></P>
<P><FONT SIZE=2>As far as ASP.NET compiling pages written in IronPython, my memory is that ASP.NET would need to be modified to recognize a new language. At least, that's the case in 1.1; it's possible that 2.0 is more extensible in this regard (wish list if not).</FONT></P>
<P><FONT SIZE=2>Speculation: you should be able to subclass Pages in IronPython, and then modify the aspx page to inherit from your IronPython class. Of course, we'd need to have compilation running (is that on the list for 1.0?).</FONT></P>
<P><FONT SIZE=2>-----</FONT>
<BR><FONT SIZE=2>Keith J. Farmer</FONT>
<BR><FONT SIZE=2>kfarmer@thuban.org</FONT>
</P>
<P><FONT SIZE=2>-----Original Message-----</FONT>
<BR><FONT SIZE=2>From: users-ironpython.com-bounces@lists.ironpython.com [<A HREF="mailto:users-ironpython.com-bounces@lists.ironpython.com">mailto:users-ironpython.com-bounces@lists.ironpython.com</A>] On Behalf Of Lorenzo Bolognini</FONT></P>
<P><FONT SIZE=2>So basically what's the story for the .NET 2 runtime support? Will you</FONT>
<BR><FONT SIZE=2>make it possible to integrate IronPy in VS .NET 2005 final release and</FONT>
<BR><FONT SIZE=2>use the .NET 2 runtime to develop ASP .NET apps?</FONT>
</P>
<P><FONT SIZE=2>If I remember correctly IronPy 1.0 will only be compatible with the</FONT>
<BR><FONT SIZE=2>1.1 runtime. Will it support something like partial classes à la C# so</FONT>
<BR><FONT SIZE=2>that the code-behind file doesn't get polluted with the IDE generated</FONT>
<BR><FONT SIZE=2>code? I wouldn't really care about other .NET 2 features if I could</FONT>
<BR><FONT SIZE=2>have that so I would happily use .NET 1.1 to develop aspx.</FONT>
</P>
<P><FONT SIZE=2>_______________________________________________</FONT>
<BR><FONT SIZE=2>users-ironpython.com mailing list</FONT>
<BR><FONT SIZE=2>users-ironpython.com@lists.ironpython.com</FONT>
<BR><FONT SIZE=2><A HREF="http://lists.ironpython.com/listinfo.cgi/users-ironpython.com">http://lists.ironpython.com/listinfo.cgi/users-ironpython.com</A></FONT>
</P>
</BODY>
</HTML>