by NGRhodes on 3/29/2023, 3:19:58 PM
by GeompMankle on 3/28/2023, 7:24:38 PM
If you spend more than 4 hours a day writing Python or you have more than 4 months of experience with Python, PyCharm. Otherwise notepad or pico or vim or emacs or whatever. It is not a good first editor as it is for professional users who need powerful tools.
by crop_rotation on 3/28/2023, 7:39:17 PM
PyCharm without a doubt. Regardless of what you are doing, you would be hard pressed to find a better IDE (e.g. You write flask apps, the IDE can take you from the template to the functions and vice versa, and similar for many other libraries and frameworks).
by jamager on 3/28/2023, 7:45:03 PM
Experience beats convenience and feature set, IMO. I use PyCharm, but I could understand coworkers who refused to move away from vim after 15 years at it.
by mindcrime on 3/29/2023, 12:38:33 AM
Eclipse with PyDev[1].
by kitrose on 3/28/2023, 7:24:15 PM
Happy Pycharm user here.
by lordkrandel on 3/28/2023, 9:51:21 PM
Neovim
by PaulHoule on 3/28/2023, 7:28:09 PM
PyCharm!
It is well worth spending time with various editors/IDEs as YMMV.
Currently we have a really great choice of IDEs/editors (and supporting tools) not just for python, but most languages and workflows.
It's also worth noting that your choice/usage of IDE's should be considered along side other tooling you have, for example if you have a CI server or actions on commit that do code quality checks, then you may not need to rely on (as much) code quality features of your IDE, or maybe you have some great scripts that run pylint, flake8, mypy, jedi on your project and create you a nice report. There is nothing wrong with supplementing your editor/ide, don't be a martyr to a specific IDE/editor.
My current personal favourite is Pycharm.
I've only been using it a few months on a 17939 loC existing, new to me project. The biggest thing I am liking at the moment, is the ability to view/pin multiple search/problem tabs and have them in their own search/problem windows.
I am finding code quality inspection (errors, warnings linting etc) and refactoring are significantly more detailed than VSCode with pylance and have a few examples where pylance gets things wrong with its inspections, that Pycharm gets right.
I am finding once a project is loaded and indexed (which is very slow compared to VSCode/pylance), the performance is comparable.