Loading…
4
DAE keep a junk file just for printing what a function returns
Three weeks ago in my Python class at the library in Reno, my loop kept spitting out None and I could not see why, so I started dumping every result into a scratch file before touching the real code. Now I catch the bug in 30 seconds instead of staring at the terminal for an hour, does anyone else do this or am I just making extra work?
1 comments
Log in to join the discussion
Log In1 Comment
the_miles13d ago
Wait, you were doing this three weeks into a Python class? That part is blowing my mind. Most folks in a beginner class are still figuring out why their print statement needs parentheses, and you already built yourself a whole debug system. A scratch file for dumping return values is honestly what half the pros do, it's not extra work at all, it's just logging before you know the word for it. The None thing trips up everybody because a function with no return statement just quietly hands you nothing back. Keep doing it, but maybe name the file something better than junk so you can find it later when you actually need those dumps.
10