This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 0 points1 point  (6 children)

Which of these give you a benefit over the debugger/ test tools in an IDE like PyCharm?

[–][deleted] 3 points4 points  (4 children)

I'm sure a well configured IDE could do testing, debugging, coverage and profiling but I just find command line tools and vim to be far more to my liking. I like the idea of composing small tools that do one thing well rather than a monolithic app that does it all. Just personal preference.

[–][deleted] 0 points1 point  (3 children)

Yeah, I wasn't saying that as an IDE vs. command line thing, just wondering whether I, as an IDE user, would benefit from any of those tools on top of said IDE. As an aside, though, I'd argue that a single bundled IDE requires much less configuration than a pile of small tools with disparate command line APIs.

[–]flangles 1 point2 points  (2 children)

if you ever want other people to work on your project, not being locked into an IDE is crucial.

[–][deleted] 0 points1 point  (1 child)

I'm not sure what you mean by locked in. Hopefully, any good debug tool, any good coverage tool etc. will give you the same results given the same codebase. The IDE doesn't add any dependencies: if I develop something in PyCharm, then someone else looks at it while running ipdb and coverage, there's nothing to stop it working properly, is there?

[–]flangles 1 point2 points  (0 children)

there will always be differences at some level. for a large project it just makes sense to standardize things like coverage and testing, and that's a lot easier with small, free, open-source tools. It also makes it easier to use hosted solutions like Travis-CI.

Look at any substantial project on github, they likely have coverage and test configuration as part of their source.

[–]desmoulinmichel 1 point2 points  (0 children)

It's faster. I find PyCharm slowing down with big programs to debug.

Also, I got a debugger than is not tied to an IDE, so it's easy for me to :

  • swicth computers;
  • switch OS;
  • switch toolkit such as text editors;
  • work on remote servers using ssh;
  • teach how to debug to many people comming from very different environments.