[IronPython] Issue Triage

Dino Viehland dinov at microsoft.com
Fri Jan 7 19:28:51 CET 2011

Jeff wrote:
> On Fri, Jan 7, 2011 at 11:12 AM, Dino Viehland <dinov at microsoft.com>
> wrote:
> > 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.
> Works for me. There's a 3k release already, so I've just used that.
> Was there a difference in intent between 3k and Future? If not, I'll collapse
> them into one or the other (so far, Future has more, so I'm leaning that way).

Yep, there's a difference.  3k is things that we do actually think we'll do in 3k.
Future represents issues which are effectively intractable right now - it's kind
of a mix between "Won't Fix" (yeah, that's a problem, but it doesn't really seem
to matter), "Can't Fix" (it's simply impossible - maybe just right now, maybe forever) 
or "Crazy Hard To Fix" (maybe if we re-write the CLR or something we could fix 

In general we would put bugs there so that A) We didn't have to consider them all
of the time but B) people could continue to vote on them and/or if a solution became
available we could implement.

More information about the Ironpython-users mailing list