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.

[–] eager_eagle@lemmy.world 11 points 4 days ago (2 children)

how's that the same thing as in the picture?

[–] hellfire103@lemmy.ca 7 points 3 days ago* (last edited 3 days ago) (1 children)

Here it is in greentext form:

>"error on line 42"
>look inside
>no code on line 42

mfw python throws errors about other peoples code

[–] eager_eagle@lemmy.world 3 points 3 days ago (1 children)

Python stack traces give you all files involved in the error, with their lines. I don't know what you're talking about

[–] irelephant@lemmy.dbzer0.com 8 points 3 days ago* (last edited 3 days ago)

hence the

which are easily confused with my own code if I’m tired and don’t read the message properly.

[–] CallMeAl@piefed.zip 7 points 3 days ago (1 children)

it happens all the time in bash. i write some and there's no error but everyone complains that i didn't use brainfuck

[–] diffaldo@lemmy.dbzer0.com 4 points 3 days ago

You dont like brainfuck!?😨

[–] ZoteTheMighty@lemmy.zip 4 points 3 days ago

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.