Re: [IronPython] -i option doesn't go interactive when exception is raised

2006-03-13 Thread Dino Viehland
Thanks for the bug report Seo, we'll look into getting it fixed for beta 5.


Do you want to help develop Dynamic languages on CLR? 
(http://members.microsoft.com/careers/search/details.aspx?JobID=6D4754DE-11F0-45DF-8B78-DC1B43134038)

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sanghyeon Seo
Sent: Sunday, March 12, 2006 6:24 AM
To: Discussion of IronPython
Subject: [IronPython] -i option doesn't go interactive when exception is raised

One use of -i option is to inspect stack trace when exception is raised.

# test.py
1/0

$ python -i test.py
...
ZeroDivisionError


This way one can inspect variables at the time exception was raised.
Sure, debuggers can do that, but simple -i option is sometimes handy.

IronPython implements -i option, but it doesn't go interactive when
exception is raised.

Seo Sanghyeon
___
users mailing list
users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
___
users mailing list
users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com


[IronPython] -i option doesn't go interactive when exception is raised

2006-03-12 Thread Sanghyeon Seo
One use of -i option is to inspect stack trace when exception is raised.

# test.py
1/0

$ python -i test.py
...
ZeroDivisionError


This way one can inspect variables at the time exception was raised.
Sure, debuggers can do that, but simple -i option is sometimes handy.

IronPython implements -i option, but it doesn't go interactive when
exception is raised.

Seo Sanghyeon
___
users mailing list
users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com