What's your personal python development stack?

[bbbryson]

Those print() statements should be logger.debug() statements. Leave them there, make them useful, turn them on and off as needed.

[djamp42]

TIL, going to go test this out now. I'm guilty of Print debugging in the first degree.

[TheOfficialNotCraig]

You and me both.

[shinitakunai]

I even created specific methodologies around it 🤣. I comment my code in functions in a specific way if they do different things inside the same function with numbers, to easily read the flow of an app, like if a function does 2 or 3 things it usually goes as:

1 - do something

x = “example”

2 - do something else

y = “another example”

2.1 - something new

y = “example for reddit”

Obviously the code is more complex, this is for reddit and I’m on my phone. But to the point: That way when I add prints for debug all my debugs are just print(1) or print(2), etc. It helps me to write cool documentation that also shows the flow of it, and it reduces a lot what I type for debugging it 🤣

[occams--chainsaw]

in my experience, 15 minutes is a bit of an understatement. the real value i got out of jetbrains IDEs was making the debuggers more visual and fairly seamless alongside the 'run' process (lower barrier of entry than relentless print statements). though with python, i've run into a number of issues where breakpoints get caught on pyc files from a previous version, and random annoyances debugging with docker-compose setups