[IronPython] Issue Triage

Dino Viehland dinov at microsoft.com
Fri Jan 7 19:12:45 CET 2011

Jeff wrote:
> > I think the following needs some further scrutiny before closing:
> >
> > module globals are reported incorrectly to sys.settrace
> > (http://ironpython.codeplex.com/workitem/26243)
> > Finish FunctionEnvironment cleanup
> > (http://ironpython.codeplex.com/workitem/23992)
> > Unable to set value type's field even with the help of StrongBox
> > (http://ironpython.codeplex.com/workitem/23998)
> Dino, can you look at these? They look fixed to me, but I'm not sure.

I've closed 26243 and 23992, I need to look at 23998 a little deeper to make
sure it's fixed.

> > One issue that I think should be fixed for 2.7 is this one:
> >
> > binder failed to make the choice when non-generic/generic methods have
> > the same signature (http://ironpython.codeplex.com/workitem/23999)
> >
> > Since Python doesn't deal with generics I would think the
> > least-surprise outcome would be for the C# spec to be followed for
> overload resolution.
> This would be a good task for anyone who really wants to learn the guts of
> IronPython. Sadly, I don't have the time :(

I've added a comment to this one.  Personally my vote is (and has been for some
Time) to move all method binder bugs to IronPython 3k.  Method binding is subtle 
enough and changing it could break existing code that we should tread carefully.  
Also this bug has been there since 2007 and no one seems to have run into it in 
the real world.  

More information about the Ironpython-users mailing list