Ok, I'll keep it as a 1.01 bug for now and set the priority as high so make sure we get to it before it becomes critical :).
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jan Szumiec Sent: Monday, August 07, 2006 8:30 AM To: Discussion of IronPython Subject: Re: [IronPython] AttributeError problem Dino Viehland wrote: > Thanks for the bug report. I've opened CodePlex bug #1689 to track this > (http://www.codeplex.com/WorkItem/View.aspx?ProjectName=IronPython&WorkItemId=1689) > . > > Just to make sure we get the correct priority - is this blocking you? My > only concern is that the fix here could be a little destabilizing. The point > when we're catching the wibble exception and the point where we re-throw the > fish exception are rather disconnected. We'd like to minimize the churn now > that we're at the end game so if it's not a blocker it might be better to > wait for this one until 1.01. If it is a blocker let us know and we'll take > a closer look at it. Thanks! > It is preventing us from returning meaningful error messages to our users. It's not critical at the moment. Thanks, Jan _______________________________________________ users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com _______________________________________________ users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
