Issue9

Title In tracebacks Nuitka uses start of call line, whereas CPython uses end of call line (help wanted)
Priority wish Status in-progress
Superseder Nosy List kayhayen
Assigned To kayhayen Keywords help_wanted, wrong_execution

Created on 2011-11-10.00:13:54 by kayhayen, last changed by kayhayen.

Messages
msg389 (view) Author: kayhayen Date: 2013-06-30.07:16:42
Partly fixed for 0.4.4, arguments that cannot raise, but come last, can still 
trigger such issue.
msg370 (view) Author: kayhayen Date: 2013-06-15.06:31:03
The new ordered evaluation args implementation, allows to support this.
msg54 (view) Author: kayhayen Date: 2012-01-13.05:41:14
It affects many CPython tests when run with the wrong CPython version.
msg22 (view) Author: kayhayen Date: 2011-11-10.00:14:42
If anyone were to step up and research this further, I would be glad.
msg21 (view) Author: kayhayen Date: 2011-11-10.00:13:54
The Nuitka behaviour is more readable, you get

> called (

instead of

> )

in the traceback, where the CPython line doesn't give any clue.

Still this is an incompatbility, that needs to be addressed. We can consider 
making the compatible behaviour optional, and use it for the tests only.

The underlying problem is that the "ast" parse function doesn't give us the end 
of the call anywhere, or at least I didn't find it. One wonders, how CPython 
achieves it. Ultimately it may be needed to parse the function call ourselves, 
which could be achieved by bracket matching.
History
Date User Action Args
2013-06-30 07:16:42kayhayensetassignedto: kayhayen
messages: + msg389
2013-06-15 06:31:03kayhayensetstatus: deferred -> in-progress
messages: + msg370
2012-01-13 05:41:14kayhayensetmessages: + msg54
2011-11-10 00:14:42kayhayensetmessages: + msg22
title: In tracebacks Nuitka uses start of call line, whereas CPython uses end of call line -> In tracebacks Nuitka uses start of call line, whereas CPython uses end of call line (help wanted)
2011-11-10 00:13:54kayhayencreate