Issue1201

classification

Title:	Lack of Python line numbers in Java tracebacks
Type:	behaviour	Severity:	normal
Components:	Core	Versions:	2.5b0
		Milestone:

process

Status:	closed	Resolution:	fixed
Dependencies:		Superseder:
Assigned To:	fwierzbicki	Nosy List:	fwierzbicki, pjenvey
Priority:	urgent	Keywords:

Created on 2008-12-11.04:43:24 by pjenvey, last changed 2008-12-14.01:05:43 by pjenvey.

Messages
msg3913 (view)	Author: Philip Jenvey (pjenvey)	Date: 2008-12-11.04:43:23
The move to the asm compiler branch lost the handy .py line numbers in tracebacks: java.lang.Exception: Stack trace at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:16 3) at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:17 1) at org.python.core.PyObject.__call__(PyObject.java:266) at org.python.pycode._pyx2.load_module$22(Lib/test/test_importhooks.py) at org.python.pycode._pyx2.call_function(Lib/test/test_importhooks.py) at org.python.core.PyTableCode.call(PyTableCode.java:199) We've talked a few times about adding them back via JSR-45 facilities -- I'm logging this as a reminder It makes debugging harder if you're dealing with a Java stack trace and is a regression from the 2.2 release
msg3917 (view)	Author: Philip Jenvey (pjenvey)	Date: 2008-12-14.01:05:42
Frank fixed this in r5756

History
Date	User	Action	Args
2008-12-14 01:05:43	pjenvey	set	status: open -> closed resolution: fixed messages: + msg3917
2008-12-13 01:49:07	fwierzbicki	set	assignee: fwierzbicki nosy: + fwierzbicki
2008-12-11 04:43:24	pjenvey	create