That’s our goal but unfortunately there isn’t really much new in there yet (from 1.1 w/ -X:Python25). We have changed the default to having the v2.5 features enabled now and no longer have a mode which runs as 2.4.
Major things we know we still have to do include yield expressions (sorry, there’s probably a technical term for them) and switching to new-style classes for exceptions. There’s also a lot of random new functions added we don’t yet have. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of M. David Peterson Sent: Tuesday, July 10, 2007 12:17 PM To: Discussion of IronPython Subject: Re: [IronPython] Hosting IronPython 2.X in .NET app On 7/6/07, JoeSox <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote: One of the reasons why I haven't updated IronTextBox is that IronPython 2 is in Alpha. I decided to wait until it was Beta. On top of that, Python is set for a major version upgrade soon, so I don't know how this will effect IronPython's development. I am wondering if others are thinking the same? I don't remember if it was a post to this list, or a blog entry, or a white paper overview, or etc., but if not mistaken there is a considerable amount of focus being placed on making IP 2.0 Python 2.5 compliant as well as at least some effort at adding some of the Python 3000 features. Can someone at MSFT verify? -- /M:D M. David Peterson http://mdavid.name | http://www.oreillynet.com/pub/au/2354 | http://dev.aol.com/blog/3155
_______________________________________________ users mailing list users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
