Spent 2 hours trying to fix a typo I made in the first line

I was working on my first Python project last night, a simple calculator. I kept getting a syntax error and could not figure out why for two hours. Turns out I spelled 'print' as 'prnit' right at the start. Has anyone else spent way too long tracking down a stupid mistake like that?

2 comments

2 Comments

the_richard1mo ago

Three hours hunting a syntax error and it was just "prnit" instead of "print." I've been there with missing semicolons in PHP, spent an entire afternoon on one stupid character and wanted to flip my desk. Worst part is you know it's going to be something tiny, but your brain still refuses to see it until you're about to give up completely.

lee.diana1mo ago

Ugh I feel this so hard. One time I was debugging a JavaScript loop for like three hours and it turned out I had used a comma instead of a semicolon in the for statement, like for(i=0, i<5, i++) instead of semicolons. My brain just skipped right over it every single time I read through the code. It's always the dumbest little thing that wastes the most time, makes you want to throw your laptop out the window.

-1