[issue44576] AttributeError: incorrect line identified in Python 3.10

Change by Mark Shannon : -- priority: release blocker -> resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___

[issue44576] AttributeError: incorrect line identified in Python 3.10

Pablo Galindo Salgado added the comment: > I'm inclined to leave it as is I am fine with that, if you think this is not a bug, close the issue and remove the release blocker :) -- ___ Python tracker

[issue44576] AttributeError: incorrect line identified in Python 3.10

Andre Roberge added the comment: While I filed the original report, I am in agreement that accurate information for debugging tools is definitely more important than the quick summary shown in the traceback, and that the change likely represents an improvement in situations more realistic

[issue44576] AttributeError: incorrect line identified in Python 3.10

Mark Shannon added the comment: This is a tricky one. Which is the "correct" line appears to be subjective. I'm inclined to leave it as is, as the tracing sequence seems better in the case of method chaining. See https://github.com/python/cpython/blob/main/Lib/test/test_compile.py#L890

[issue44576] AttributeError: incorrect line identified in Python 3.10

Pablo Galindo Salgado added the comment: Mark, take a look as soon as possible as beta4 is this week -- nosy: +pablogsal priority: normal -> release blocker ___ Python tracker

[issue44576] AttributeError: incorrect line identified in Python 3.10

Alex Hall added the comment: (meant to say "so I'm pulling in @Mark.Shannon) -- ___ Python tracker ___ ___ Python-bugs-list

[issue44576] AttributeError: incorrect line identified in Python 3.10

Alex Hall added the comment: I believe this is the outcome of https://bugs.python.org/issue39316 which I filed, so I'm pulling in . Naturally I think the new behaviour is not a bug but a feature. I think it's more important for the traceback to show the attribute access (`two`) than the

[issue44576] AttributeError: incorrect line identified in Python 3.10

New submission from Andre Roberge : Consider the following program # example.py one = 1 two = "two" a = [one . two] Running this program with Python versions before 3.10, yields the following traceback: Traceback (most recent call last): File "C:\Users\andre\example.py", line 3,