Re:Show HN: PyScribe – A Python library to make print debugg...
by kelvin0 on Saturday January 03, 2015 @07:16PM
(#8832605)
But, it's dead simple to use an IDE. Plus the code you debug within the IDE is the same as the production code.
It allows to use breakpoints, and watch vars.
There are a bunch of free IDEs, what don't you like about using one?
Re:Show HN: PyScribe – A Python library to make print debugg...
by alixander on Saturday January 03, 2015 @10:22PM
(#8833124)
You think you misunderstood; I didn't try it and not like it, I just never tried it. I'm most productive on Vim/Terminal right now. From a quick google search, it doesn't seem like I can use all the Vim commands in an IDE (though I see some articles on using Vim AS an IDE). Have you personally tried both and preferred an IDE over Vim/Terminal?
I'll be adding more documentation soon, but perhaps this is a more informative use case: Too often in my Python programs, I'll do something like, print("x is: " + str(x)). That's already too much to keep typing, but sometimes I'll want to know the type, or maybe it's a dictionary and printing without separators makes them blend together (say, in a for loop). In that case, I'll do: print("---------\nx is: " + str(x) + "\n")
The library allows this to be simplified to "ps.d(x)". It's rather opinionated towards my own workflow and what I was too lazy to keep doing. Perhaps I'll try pdb one day and find my library useless.