There will certainly be some 2.6 features. But we still haven't quite figured out what "2.1" is yet. So if there's a particular 2.6 feature, or if you'd just like us to see us do them all, let us know - same goes for other features, fixes, misc improvements, etc...
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Vernon Cole Sent: Friday, October 31, 2008 6:02 PM To: Discussion of IronPython Subject: Re: [IronPython] 2.1 Branch in Codeplex Sources "IronPython 3k"... does that mean that IPy 2.1 is targeted to be compatible with CPython 2.6? (Please say "yes"!) -- Vernon Cole On Fri, Oct 31, 2008 at 10:30 AM, Dino Viehland <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote: Just one other comment on top of what Curt said. You might more properly think of Main as IronPython 3k. Main includes a ton of renames and other breaking made in Microsoft.Scripting.Core/System.Core that will end up in .NET 4.0. We're still working on what we want to do for 2.1 (and input is always welcome of course) but our current thinking is that it will be API compatible w/ 2.0.
_______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
