[IronPython] IronPython 2.0 Errors...

António Piteira antonio.piteira at wtvision.com
Fri Jan 23 18:14:04 CET 2009

I get it, I’m not really surprised
 I was hoping that maybe there was a way
to use scriptSource.Compile(options,errorTracker), or something like that,
and get the errors from errorTracker or some kind of sink.


Very much apreciated for your time.





Are you familiar with "the halting problem"? :) (


The only reliable way to find if a particular program returns a runtime
error is to execute the program.  For limited, targeted cases, (such as
importing modules) you could write an analyzer program which would be
*often* right -- but I could create a program  that tricks your analyzer
into reporting a problem where none exists.  Consider this:


import sys

sys.modules['foo'] = type(sys)('foo')

import foo


Your static analyzer would have a tough time recognizing that this program
would not raise a runtime error.




Those things are run-time errors (failed imports et al). You would

possibly look at the parse tree for any imports and determine if the

modules to be imported exist, but that sounds like a lot of trouble :)






On Fri, Jan 23, 2009 at 8:45 AM, António Piteira
<antonio.piteira at wtvision.com> wrote:



I'm trying get all runtime errors without actually executing the code. I can
get all syntax errors using the parser, but runtime errors like "import ys"
and stuff like that I', not able to.

Is there any way to do this?




Users mailing list
Users at lists.ironpython.com


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ironpython-users/attachments/20090123/7a97c75e/attachment.html>

More information about the Ironpython-users mailing list