3 ms·

Outside of scientific computing, I typically go to Spyder on one-off scripts and smaller projects. I like Spyder over PyCharm for smaller projects because ther

Outside of scientific computing, I typically go to Spyder on one-off scripts and smaller projects. I like Spyder over PyCharm for smaller projects because there's less startup cost and the code cells functionality is handy for the "edit and run this part until it does what I want" style of coding, which makes the bulk of my time in small projects. For bigger projects, PyCharm's refactoring, commit diffing, code regions, and formatting are enough better to be worth the fuss. As a rule of thumb, if I'm going to bother to set up a dedicated environment / git repo / file structure / test suite, I'll typically use PyCharm, else Spyder.

lytefm 6y ago
> and the code cells functionality is handy for the "edit and run this part until it does what I want" style of coding, which makes the bulk of my time in small projects. Yes, I love this „quick and dirty” interactive style within Spyder too, but switch to PyCharm when I need to refactor, work with larger project or test. Sometimes I'd switch multiple times per day for the same project, so having a more Spyder-like DS tool under development at JetBrains seems to be good news.