That happens all the time with Python. It often shows me errors in the imported modules, which are easily confused with my own code if I’m tired and don’t read the message properly.
It can also happen in Python if you edit the file after runtime. It parses the code on import, but re-reads the file as text during the error message, so if you added or deleted lines, the error report can report a dubious line.
That happens all the time with Python. It often shows me errors in the imported modules, which are easily confused with my own code if I’m tired and don’t read the message properly.
It can also happen in Python if you edit the file after runtime. It parses the code on import, but re-reads the file as text during the error message, so if you added or deleted lines, the error report can report a dubious line.
how’s that the same thing as in the picture?
Here it is in greentext form:
Python stack traces give you all files involved in the error, with their lines. I don’t know what you’re talking about
hence the
it happens all the time in bash. i write some and there’s no error but everyone complains that i didn’t use brainfuck
You dont like brainfuck!?😨