On Fri, Jan 7, 2011 at 11:12 AM, Dino Viehland <di...@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). - Jeff _______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
