[issue20613] Wrong line information in bytecode generated by compiler module

Brett Cannon added the comment: Since 2.7 development is done there is no compiler packages anymore to worry about. :) -- resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker

[issue20613] Wrong line information in bytecode generated by compiler module

Change by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue20613] Wrong line information in bytecode generated by compiler module

Changes by Mark Lawrence breamore...@yahoo.co.uk: -- nosy: +benjamin.peterson, brett.cannon, georg.brandl, ncoghlan ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20613 ___

[issue20613] Wrong line information in bytecode generated by compiler module

Arnaud Fontaine added the comment: compiler module being deprecated does not mean that it's not used. For example, it is used by RestrictedPython as part of Zope2. As I could not figure out a way to fix this bug properly, I reverted the following commit and have not had any problem so far

[issue20613] Wrong line information in bytecode generated by compiler module

Mark Lawrence added the comment: Am I correct in assuming that we'd need to fix a regression in 2.7 owing to its extended life span, or would the compiler being deprecated make this not worth the trouble, or what? -- nosy: +BreamoreBoy ___ Python

[issue20613] Wrong line information in bytecode generated by compiler module

New submission from Arnaud Fontaine: I know that compiler module is deprecated since 2.6, but I found a regression introduced in version 2.7 by the following cleanup commit (replacing pyassem.py modified in this commit by the one just before does not trigger this bug):