This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author serhiy.storchaka
Recipients Thomas Haller, serhiy.storchaka
Date 2019-09-26.15:01:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1569510077.07.0.58672066097.issue38283@roundup.psfhosted.org>
In-reply-to
Content
No, I do not know such workaround. At best, you can analyze the code object and get the line number of the next instruction. It may be the line past the last line of the function call, or be equal to it if the function call is the part of complex expression or if you write several statements on the line. Then you need to analyze the sources.

The information about the first line of the multiline expression looks more useful than information about the last line. And it is more consistent with other cases. Maybe in future we will add information about the range of lines for every expression and statement (some steps was already made in this direction). But this is more complex change.
History
Date User Action Args
2019-09-26 15:01:17serhiy.storchakasetrecipients: + serhiy.storchaka, Thomas Haller
2019-09-26 15:01:17serhiy.storchakasetmessageid: <1569510077.07.0.58672066097.issue38283@roundup.psfhosted.org>
2019-09-26 15:01:17serhiy.storchakalinkissue38283 messages
2019-09-26 15:01:16serhiy.storchakacreate