News for hackers. Stuff that matters.
Re:BeeWare – The IDEs of Python by BozeWolf on Thursday May 28, 2015 @11:00AM (#9618574)
PyCharm's debugger is awesome. [1] It really is faster then the import pdb;pdb.settrace(). (which happens to get committed sometimes). Code coverage displaying is really well implemented. Autocompletion and introspection is great. On a lot of frameworks as well. Continuously displays python linting issues and suggests fixes. Vagrant support works really good, even for remote debugging and running tests/devservers. The git implementation is quite useful, although I do fall back on command line every now and then. You can customize pycharm's interface a lot (impossible to explain in just a line or 2). If you like to edit distraction-free... there is a mode for that too. It has an internal git system. So if you screw stuff between git commits, you can revert to a previous version nonetheless (local version) There are a few ways to open files: a tree view, an "alfred"-like method and probably more.

1: https://www.jetbrains.com/pycharm/features/#debugger

Things i do not use: The internal terminal; iTerm just is a lot better. The interal ipython console. I prefer iTerm + iPython. FTP and oldschool stuff like that. Did not try the new profiling feature yet.

Re:BeeWare – The IDEs of Python by crimsonalucard on Thursday May 28, 2015 @11:43AM (#9618901)
You should note remote debugging is awesome too. You can remote into external servers or even a local vagrant and debug it as if it was local code.
Re:BeeWare – The IDEs of Python by vosper on Thursday May 28, 2015 @12:50PM (#9619414)
Do you ever have problems with the debugger losing its place, failing to step properly, or not being able to evaluate commands, when using a VM with Vagrant? I was really excited to get PyCharm working with our development VM, but these issues made the debugger useless for me.
Re:BeeWare – The IDEs of Python by crimsonalucard on Thursday May 28, 2015 @01:38PM (#9619746)
The only issue I had was sometimes the debugger wouldn't stop at a breakpoint, but this was rare and easily dealt with by putting a small cluster of breakpoints at the problem area.
Re:BeeWare – The IDEs of Python by dr_zoidberg on Thursday May 28, 2015 @11:09AM (#9618657)
Hmmm will be looking into the debugger!