On Mon, Dec 1, 2008 at 12:26 PM, Dino Viehland <[EMAIL PROTECTED]> wrote: > Thanks for reporting & opening the bug. The fix for this is likely fairly > easy but I don't think we'd spin a new 2.0 build for just this issue because > it isn't really blocking anything as you have a work around. > > That being said it would certainly be something we'd fix for 2.0.1 and we > don't expect the time between 2.0 and 2.0.1 to be particularly long. But if > we were to spin a new 2.0 build for some other reason (which I'm a little > worried we might need to do) we might just include this fix.
I agree, no need to hold 2.0 just for this little bug. -Jeff _______________________________________________ Users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
