[IronPython] Multiple engine instances in IP 2.0 and beyond (was IronPython 2.0 Alpha 1 Released)

Michael Foord fuzzyman at voidspace.org.uk
Wed Jun 6 12:24:39 CEST 2007


Shri Borde wrote:
> I agree that you should stick with 1.1 if you are close to release.
>
> We will fix critical blocking bugs in 1.1 as needed. However, to keep that branch stable, the bar will be high. Do shout if you run into blocking issues.
>   

Yes, this is our plan. Thanks for your support.

At the moment there are no blocking bugs. Rest assured that we will let 
you know if we encounter any. :-)

Thanks

Michael Foord
http://www.voidspace.org.uk/ironpython/index.shtml


> -----Original Message-----
> From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of Fuzzyman
> Sent: Tuesday, June 05, 2007 2:30 AM
> To: Discussion of IronPython
> Subject: Re: [IronPython] Multiple engine instances in IP 2.0 and beyond (was IronPython 2.0 Alpha 1 Released)
>
> Shri Borde said:
>
>   
>>> Have you looked at moving to 2.0? Dino had mentioned a workaround (of maintaining a thread-local static) which would enable you to selectively redirect console output. Given that you are running into a number of issues and that you might have a stream of such issues going forward, it will be hard for us to continually port all those fixes to 1.1.
>>>
>>>
>>>       
>
> None of the 1.1 bugs are blocking us, we have just discovered them as we
> develop. If we encounter a blocking bug we will shout loudly. :-)
>
> Given that we are so close to release, and that switching to 2.0 will
> mean non-trivial changes (which wasn't true of 1.0 - 1.1 - thank you),
> we will stick to 1.1 for the moment. Eventually we will have to move to
> 2.0 of course (and would like to).
>
> As 2.0 is still in alpha, we would like to think that the 1.X branch
> hasn't been abandoned by 'the team'.
>
> In the very long run we will move to executing user code inside
> appdomains, but currently that would result in a lot of cross domain
> calls that would hurt our performance in a big way. As resolving this
> would be a lot of work it isn't yet a high priority for us - and won't
> be for quite a long time.
>
> All the best,
>
>
> Michael Foord
> http://www.voidspace.org.uk/ironpython/index.shtml
> _______________________________________________
> 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
>
>   




More information about the Ironpython-users mailing list