You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using IPython, the "filename" contains the number information of the code block that contains it; this is something of the form <ipython-input-N-...> where N is the code block number.
When actual temporary files are used in the ipykernel, the names created on
lose that information.
My suggestion would be to append _number to the filename where number is the code block number. So, instead of path/to/filename.py one would have path/to/filename_number.py. This would enable a human reader to identify which code block is involved in the traceback.
Additionally, while it is currently possible to programmatically obtain the information and having a "filename" much more understable, as demonstrated in the image below, there can be some ambiguity if the exact same content appears in two code blocks, one of which appearing in a traceback (as shown in the second traceback in the image below).
Adding the _number would remove this ambiguity.
The text was updated successfully, but these errors were encountered:
When using IPython, the "filename" contains the number information of the code block that contains it; this is something of the form
<ipython-input-N-...>
whereN
is the code block number.When actual temporary files are used in the ipykernel, the names created on
ipykernel/ipykernel/compiler.py
Line 50 in b2f1a79
My suggestion would be to append
_number
to the filename wherenumber
is the code block number. So, instead ofpath/to/filename.py
one would havepath/to/filename_number.py
. This would enable a human reader to identify which code block is involved in the traceback.Additionally, while it is currently possible to programmatically obtain the information and having a "filename" much more understable, as demonstrated in the image below, there can be some ambiguity if the exact same content appears in two code blocks, one of which appearing in a traceback (as shown in the second traceback in the image below).
Adding the
_number
would remove this ambiguity.The text was updated successfully, but these errors were encountered: