[IronPython] IronPython 1.1.2 eta?

Michael Foord fuzzyman at voidspace.org.uk
Tue Jul 1 17:19:21 CEST 2008


Dino Viehland wrote:
> We're not going to do that anytime soon - but there will be a point in the future when we require a more recent .NET than 2.0.  Our current thinking is that happens when pieces of the DLR move into the .NET framework.  We'll then have a major new version - e.g. 3.0.  But it's not going to happen anytime too soon.  We currently think all releases in 2.x will forever require .NET 2.0 SP1 as their minimum bar.
>
>   
Ok - cool.

Michael

> -----Original Message-----
> From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of Michael Foord
> Sent: Tuesday, July 01, 2008 1:28 AM
> To: Discussion of IronPython
> Subject: Re: [IronPython] IronPython 1.1.2 eta?
>
> Dino Viehland wrote:
>   
>> The good news is this is basically inevitable but will take some time to achieve :).  In the latest source code, I guess currently available only through the IronRuby SVN, you'll see that the namespaces of the DLR expression trees have moved to System.Linq.Expressions.  This is the completion of making the DLR expression trees into a superset of the LINQ expression trees.
>>
>> Unfortunately both of your features require taking a dependency on .NET 3.5 (or some future version) which we're just not quite ready to do.  But ultimately this should be trivial in the future - it's just not going to happen in 1.x and probably not 2.x.   But the lambdas -> expression trees is probably a little easier as it's just add some new conversion support - C# 3.0 extension methods have scoping design issues.
>>
>>     
>
> Please don't make .NET 3.5 a dependency for IronPython!
>
> As an option for additional Linq support in IronPython it would be
> *great*, but not as a requirement...
>
> Thanks
>
> Michael Foord
>
>   
>> Anyway obviously this is something we care about too but it serves as a good excuse to mention some cool recent code changes :).
>>
>> -----Original Message-----
>> From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of Keith J. Farmer
>> Sent: Monday, June 30, 2008 9:26 PM
>> To: Discussion of IronPython
>> Subject: Re: [IronPython] IronPython 1.1.2 eta?
>>
>> (Python lambdas to CLR Expression Trees.. my one wish aside from C#3-style extension method resolution)
>>
>> (but y'all knew that, anyway)
>>
>> -----Original Message-----
>> From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of Dino Viehland
>> Sent: Monday, June 30, 2008 1:00 PM
>> To: Discussion of IronPython
>> Subject: Re: [IronPython] IronPython 1.1.2 eta?
>>
>> Yeah, it's not going to happen today :)  The changes are done (any bugs assigned to me and the 1.1.2 release on CodePlex will be fixed), they just need to run through a full test pass.  I got started on the changes late and the test infrastructure needed to be brought back to life so it's taking a little bit longer than expected but the RC should be out soon.
>>
>> Beta 4 is currently planned for early August.  If you're willing to try out a source release from http://www.codeplex.com/IronPython/SourceControl/ListDownloadableCommits.aspx I'd be happy to let you know when the last remaining regression is fixed (and gets uploaded there - looks like that hasn't been happening :().  We've fixed the polymorphic call site perf bug already but there's still a bug that results in massive overhead of calling simple Python functions.
>>
>> -----Original Message-----
>> From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of Michael Foord
>> Sent: Monday, June 30, 2008 11:51 AM
>> To: Discussion of IronPython
>> Subject: [IronPython] IronPython 1.1.2 eta?
>>
>> Hello guys,
>>
>> A while back you suggested that IronPython 1.1.2 would arrive 'some time
>> in June'. Whilst that is still possible it seems unlikely, any news on
>> an eta?
>>
>> Whilst we're at it, any idea on when IP 2 Beta 4 might be released? We'd
>> like to test Resolver One with an updated IronPython 2 where performance
>> isn't borked quite so much... :-)
>>
>> Michael
>>
>> --
>> http://www.ironpythoninaction.com/
>> http://www.voidspace.org.uk/
>> http://www.trypython.org/
>> http://www.ironpython.info/
>> http://www.theotherdelia.co.uk/
>> http://www.resolverhacks.net/
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.ironpython.com
>> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
>> _______________________________________________
>> Users mailing list
>> Users at lists.ironpython.com
>> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
>> _______________________________________________
>> Users mailing list
>> Users at lists.ironpython.com
>> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.ironpython.com
>> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
>>
>>     
>
>
> --
> http://www.ironpythoninaction.com/
> http://www.voidspace.org.uk/
> http://www.trypython.org/
> http://www.ironpython.info/
> http://www.resolverhacks.net/
> http://wwww.theotherdelia.co.uk/
>
> _______________________________________________
> Users mailing list
> Users at lists.ironpython.com
> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
> _______________________________________________
> Users mailing list
> Users at lists.ironpython.com
> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
>   


-- 
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/
http://www.trypython.org/
http://www.ironpython.info/
http://www.resolverhacks.net/
http://wwww.theotherdelia.co.uk/




More information about the Ironpython-users mailing list