Error reporting issues

[danyaPostfactum]

Go https://rawgit.com/danyaPostfactum/ace/python-worker/kitchen-sink.html and select python document.

Paste the code:

def fn():

You will not see a error because Skulpt provides wrong lineno (last + 1 line)

Paste the code:

    1

Skulpt will produce bad input error, but it should produce unexpected indent IndentationError

Skulpt throws ParseError, but it should be SyntaxError.

I didn't find an easy way to get an error message. Currently it' stored into a v property.

[bnmnetp]

There is nothing wrong with a single line def fn():

Python can not determine that the function definition statement is in error until you have an unindented line with no function body.

[rixner]

The line number that Skulpt gives for the "def fn():" example is correct, as described by Brad. This is the same thing CPython does.

However, I agree that the types of exceptions that get thrown in both cases do not match CPython. Exactly matching the particular error of a bad program that doesn't even compile has not been our highest priority, though.

All exception objects have a "toString()" method which will give you the formatted error message.

[danyaPostfactum]

Indeed. I was baffled by SublimeLinter. It shows "unexpected EOF while parsing" on line 1.
But standalone python (2.7) produces IndentationError on line 2 (that is very strange, because line 2 does not exist :) ).

I don't know why do they behave differently. Maybe SublimeLinter preprocesses results. Or maybe this is because of interpreter version difference.

First line of toString() result looks good, thanks.

[albertjan]

I believe this can be closed aswel.