Or use tests and/or a debugger. Which gives you all the listed benefits w/o an additional dependency.

Different tools for different cases. Debuggers are great for a snapshot in time but print statements are better for seeing the execution flow.

Debugging in python is already so easy with `print(f"{myvar=}")` and `breakpoint()`...

This is the correct answer. `ic(foo(123))` can be written as `print(f'{foo(123)=}')` without depending on yet another third-party library which is not pulling its weight.

Cannot recommend icecream, way too slow. But the use case of logging shines with realtime systems, or concurrent apps. You won't be able to efficiently debug them without logging. I live in my debugger, but logging is mandatory for the big picture.

I haven’t used print for debugging for ages. Now it’s all trace on azure and hope your bug ends up in the sampled data in whatever that stupid thing is called. App insights or some rubbish. Apparently a good old log file just isn’t good enough it has to be larded up with a query language. Grep was fine guys.

>Do you ever use print() or log() to debug your code?

I haven't written my own code in months at this point...kind of depressing to think about

So what do you actually do then?

My first thought as well. Debugging is actually a decent use case of AI.

I have a board with a logic analyzer, debug/flash probe, PSU, and multimeter on my desk being driven and debugged all autonomously by the AI.

While the automation and systems side of my brain is thrilled that all of this id automated and integrated, developer brain is sad

It's neat how trivial it is to do this in C, only takes a couple of macros. https://github.com/trvv/_/blob/d4899741c4f35833b8e86d16e2163...

Looks like the project has a linked repo that appears to do a similar thing for C but it doesn't generically format the arguments.

Remember COBOL's EXHIBIT?

...use slightly fancier print() instead!

why another tool for that ? think standard with other team/company and use the same integrated ones.