[IronPython] Standard Python Debugging not supported

Dino Viehland dinov at exchange.microsoft.com
Wed Oct 4 14:02:31 PDT 2006

Thanks for the feedback - I've added a comment to bug 1042 that we should look at excepthook.  Maybe this will be another one we can fit into 1.1.

Unfortunately, this one is a little more interesting.  While the functionality of calling the except hook function is easy enough, mutating sys is more difficult.  We might be able to work around mutating sys though, but we'll need to look into.

-----Original Message-----
From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of Douglas S. Blank
Sent: Wednesday, October 04, 2006 12:45 PM
To: Discussion of IronPython
Subject: Re: [IronPython] Standard Python Debugging not supported

Just thought that I would mention that we are awaiting implementation of sys.excepthook so that we can override the standard unhandled exception handing to provide students with more information on their errors. It isn't a big rush, as we may use CPython in the Spring, but if this were addressed sometime in the next 6 months, we'd be happy.

(FYI: we'll be using IronPython to control robots for intro computer science courses. The project, called Myro, is planned to be able to control most popular robots, and will take advantage of Microsoft Research's Robotics Studio as well. See http://www.roboteducation.org for more info.)



Dino Viehland wrote:
> We have a couple of bugs opened on this on CodePlex for this issue:
> 563: Support for Code Quality Tools in IronPython missing
> <http://www.codeplex.com/WorkItem/View.aspx?ProjectName=IronPython&Wor
> kItemId=563>
> 1042: Implement various sys module methods that currently throw a
> NotImplementedException
> <http://www.codeplex.com/WorkItem/View.aspx?ProjectName=IronPython&Wor
> kItemId=1042>
> We believe we know how to implement sys.settrace (we'd hook it at the
> same place we hook our recursion checks today) but we haven't had time
> to get to it yet.  Currently this is scheduled in our bug database as
> 1.1 feature (although that may be subject to change) but it's good to
> note that we are seeing additional demand for these APIs.  This will
> help us prioritize our 1.1 work better.  Hopefully we'll be able to
> get this in for 1.1 so it'll be just a short term limitation.  Thanks
> for the input!

users mailing list
users at lists.ironpython.com

More information about the users mailing list