Lukáš wrote: > This is a known issue > (http://ironpython.codeplex.com/workitem/26593?ProjectName=ironpython) > and as Dino mentioned recently it is already fixed in the main. > > Which brings a question - when is IronPython 2.6.2 scheduled for release?
We haven't quite scheduled it yet - we've been waiting to make sure there were no other regressions introduced in 2.6.1. I've seen 1 or 2 other small bugs that I think we'd like to fix. Personally I'm thinking end of June-ish but I'll need to talk to the rest of the team about it. _______________________________________________ Users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
