[issue3423] DeprecationWarning message applies to wrong context with exec()

Terry J. Reedy added the comment: Rereading this, I see interlocked behavior (implementation bug) and enhancement (design bug) issues. I have been focused on just the former. Consider the exception traceback in msg107441: there are *two* filename, line# pairs. Now consider this warning for te

[issue3423] DeprecationWarning message applies to wrong context with exec()

Zachary Ware added the comment: Sorry, Terry; I updated the resolution because the issue was not closed, and the versions to match the currently acceptable branches after a discussion at the Bloomberg sprint, but failed to elaborate on what the actual bug here is that came out of that discussi

[issue3423] DeprecationWarning message applies to wrong context with exec()

Terry J. Reedy added the comment: Zach, your header editing is inconsistent. If you think this is a bug rather than enhancement issue, please say why. Either way, what change you would make? And even if you think there is a bug, why would you make a change in maintenance releases, given that

[issue3423] DeprecationWarning message applies to wrong context with exec()

Michael Wu added the comment: I ran the examples in this thread with Python 3.5, and it appears to print out the correct line that exec() occurs on (http://codepad.org/M5CevRwT). It might be time to close this issue. -- nosy: +Michael.Wu Added file: http://bugs.python.org/file35732/tes

[issue3423] DeprecationWarning message applies to wrong context with exec()

Changes by Michael Wu : Removed file: http://bugs.python.org/file35732/testfile.py ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue3423] DeprecationWarning message applies to wrong context with exec()

Changes by Zachary Ware : -- resolution: rejected -> versions: +Python 2.7, Python 3.4, Python 3.5 -Python 3.2 ___ Python tracker ___

[issue3423] DeprecationWarning message applies to wrong context with exec()

Terry J. Reedy added the comment: New features only in 3.2 -- versions: -Python 2.5, Python 2.6, Python 3.1 ___ Python tracker ___ __

[issue3423] DeprecationWarning message applies to wrong context with exec()

Greg Hazel added the comment: Searching the file for "raise" is sort of pointless, since exec() takes a string which might have come from anywhere, and there might be any number of exec() calls in the module. See: http://codepad.org/7EBMhb0O There are at least two reasonable answers: :1: Dep

[issue3423] DeprecationWarning message applies to wrong context with exec()

Terry J. Reedy added the comment: In 3.1, I get >>> exec("1/0") Traceback (most recent call last): File "", line 1, in exec("1/0") File "", line 1, in ZeroDivisionError: int division or modulo by zero In your example, would you really prefer that the warning message start with "1" (o

[issue3423] DeprecationWarning message applies to wrong context with exec()

New submission from Greg Hazel <[EMAIL PROTECTED]>: exec()ing a line which causes a DeprecationWarning causes the warning to quote the file exec() occurs in instead of the string. Demonstration of the issue: http://codepad.org/aMTYQgN5 -- components: None messages: 70129 nosy: ghazel s