Serhiy Storchaka <storchaka+cpyt...@gmail.com> added the comment:
Yes, of course. We could keep f_lineno unchanged, despite the fact that its value can be wrong, and introduce f_lineno_new. Then we should change all code in the stdlib which uses f_lineno to use f_new_lineno, or rather, to keep absolute backward compatibility, add other duplicates: warnings.warn_new(), traceback.print_stack_new(), etc, and encourage all third-party projects to change their code too. But there are some drawbacks in such approach. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue38283> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
