IceCream – Never use print() to debug again
1–10 of 24 posts
Re: IceCream – Never use print() to debug again
#2Or use tests and/or a debugger. Which gives you all the listed benefits w/o an additional dependency.
Re: IceCream – Never use print() to debug again
#3>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
Re: IceCream – Never use print() to debug again
#4Or use tests and/or a debugger. Which gives you all the listed benefits w/o an additional dependency.
Yeah, the amount of wasted hours with 1960's teletype debugging.
Ah but servers and embedded, that is why telemetry, execution traces, and debugger controlled action points exist.
Re: IceCream – Never use print() to debug again
#5why another tool for that ? think standard with other team/company and use the same integrated ones.
Re: IceCream – Never use print() to debug again
#6Debugging in python is already so easy with `print(f"{myvar=}")` and `breakpoint()`...
Re: IceCream – Never use print() to debug again
#7Remember COBOL's EXHIBIT?
Re: IceCream – Never use print() to debug again
#8[dead]
Re: IceCream – Never use print() to debug again
#9I 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.
Re: IceCream – Never use print() to debug again
#10Debugging 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.