But I wouldn't use them as an equivalent to "multi-line comments" in another language (unless everyone else on your team reading your code is already bought in on that odd use).
Pro tip: While time-boxing and removing distractions are great for solving programming exercises, they're also great for entering a flow state for the purpose of studying at school or getting difficult tasks done at work.
I'd love to collaborate with (or shamelessly copy/mimic!) smart folks like the Pyodide devs, the PyScript devs, or @notsolonecoder... but this new REPL is so new that I doubt many WebAssembly-oriented folks have tried playing with this yet!
This thought path did inspired me to rewatch @phildini and Asheesh's talk on Python & TTYs.
It's even more interesting than I remember, possibly because I care more about TTYs now than when I fist watched it!
The next time you find an if-else in your code where both the "if" and the "else" return from the function that you're in, you could think of that "else" as unnecessary.
This post contains over 2 dozen links to Mastodon, GitHub, Twitter, or LinkedIn profiles.
I tried to drop a relevant link for every name that I mentioned. And there were so many names that I didn't mention... of folks I dined with, chatted with, watched speak, or interacted with in some other way.
💖 I'm looking forward to seeing you all again soon!
Any thoughts on whether either might matter for production code? Or insight into the CPython issues/PRs that fixed these? (I did a quick search but couldn't figure it out)
Happy to report either difference in behavior, but I don't want to clutter up the issue tracker with noise.