| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Would it be better to fix _Py_DisplaySourceLine() instead? |
Sorry, something went wrong.
|
I am not sure how would the fix look beside introducing a new return code
for cases that did not result with printing the line but also without an
error which seems more complicated.
…On Fri, Jul 23, 2021, 10:45 PM Dennis Sweeney ***@***.***> wrote:
Would it be better to fix _Py_DisplaySourceLine() instead?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#27313 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALJKHQPWWFKTA45LSTO5FS3TZHBGFANCNFSM5A4RI23Q>
.
|
Sorry, something went wrong.
|
Can we add a regression test for this? (Like the one on the BPO issue?) |
Sorry, something went wrong.
|
🤖 New build scheduled with the buildbot fleet by @isidentical for commit 8db4e0c 🤖 If you want to schedule another build, you need to add the ":hammer: test-with-buildbots" label again. |
Sorry, something went wrong.
|
It seems like refleaks bots also fail on the main too, so that can be ignored. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
There seems to be different cases where the _PyDisplay_Line() function returns 0 without displaying the actual line but also without having any errors raised.
cpython/Python/traceback.c
Lines 414 to 420 in 4512848
cpython/Python/traceback.c
Lines 436 to 446 in 4512848
This patch ensures that the line is retrieved and displayed.
https://bugs.python.org/issue43950