Skip to main content

Python: Python IDEs Panel

Python IDEs Panel

Side note: There were surprisingly few people at this talk. It seems like most Python programmers get started with either Vim or Emacs and then don't change. It's ironic that I'm so obsessed with programmer productivity given that I'm such a slow coder ;)

The panel consisted of representatives who worked on Python Tools for Visual Studio, PyCharm, Komodo IDE, Wing IDE, and a Python mode for Emacs (pythonmode.el). There was no one present to champion PyDev or NetBeans.

Michael Foord prefers Wing IDE.

Python Tools for Visual Studio has debugging support for high performance computing (HPC). It supports MPI. It can debug a program that uses multiple processes. It supports both IronPython and cPython. You can use iPython within Visual Studio to control a cluster of machines. You can write Python code to analyze the variables in the individual frames of a stack.

PyCharm makes test driven development (TDD) fast! The speaker was using PyCharm to test drive the development of a class which he was creating quickly in the test file. PyCharm can automatically create the scaffolding for a class as you use the class in your test. It can create the scaffolding for methods, add imports, add constructors, etc. all automatically as you try to use those things in your tests. It has helpful coding suggestions and refactoring support. It has code snippets. It's crazy how much it can guess what to create automatically. It has great Django support. It has Django-specific code completion. The demo for PyCharm was flat out amazing!

Komodo Edit is free and open source. However, Komodo IDE is commercial. It adds support for debugging, etc. It opens very quickly. It's good at working with multiple languages at the same time. It has an HTML preview feature that can show you an HTML page within Komodo (presumably because it's written in XUL). It has a regular expression debugger. There are about 80 extensions. In 2011, InfoWorld rated Komodo IDE as the best Python IDE.

Wing IDE is commercial. It supports multiple keyboard personalities. It has a debug shell. The debugger and intellisense work well together.

The champion for Emacs was Barry Warsaw. He showed how to integrate Pyflakes. The demo wasn't particularly inspiring.

Most of the IDEs have been around for about 10 years.

When I brought up the fact that so many successful programmers use Emacs, the general consensus was that the people who succeed using Emacs have been doing the same sort of thing for a really long time. They have it entirely in their head. They don't really need an IDE, and an IDE isn't really helpful for their situation.

Comments

Brent said…
I used Komodo Edit exclusively for a while. Contrary to the claim in the talk, it opened pretty slowly for me (but then I'm spoiled by Vim's instantaneous startup). I can't imagine that Komodo IDE loads any more quickly, given that it's Komodo Edit + More Stuff. Maybe the presenter was using a preloader?
jjinux said…
Thanks, Alex, but unfortunately, I think that's the wrong video.
jjinux said…
From Anonymous:

I use Editra which most people overlook.

It is written in Python, multi-platform through WxWidgets/WxPython, fast, lightweight and handles over 60 programming languages including Python.

I always load it into my Linux distro and download and install it onto my Mac as its handy to have around.

http://editra.org/

Popular posts from this blog

Ubuntu 20.04 on a 2015 15" MacBook Pro

I decided to give Ubuntu 20.04 a try on my 2015 15" MacBook Pro. I didn't actually install it; I just live booted from a USB thumb drive which was enough to try out everything I wanted. In summary, it's not perfect, and issues with my camera would prevent me from switching, but given the right hardware, I think it's a really viable option. The first thing I wanted to try was what would happen if I plugged in a non-HiDPI screen given that my laptop has a HiDPI screen. Without sub-pixel scaling, whatever scale rate I picked for one screen would apply to the other. However, once I turned on sub-pixel scaling, I was able to pick different scale rates for the internal and external displays. That looked ok. I tried plugging in and unplugging multiple times, and it didn't crash. I doubt it'd work with my Thunderbolt display at work, but it worked fine for my HDMI displays at home. I even plugged it into my TV, and it stuck to the 100% scaling I picked for the othe

ERNOS: Erlang Networked Operating System

I've been reading Dreaming in Code lately, and I really like it. If you're not a dreamer, you may safely skip the rest of this post ;) In Chapter 10, "Engineers and Artists", Alan Kay, John Backus, and Jaron Lanier really got me thinking. I've also been thinking a lot about Minix 3 , Erlang , and the original Lisp machine . The ideas are beginning to synthesize into something cohesive--more than just the sum of their parts. Now, I'm sure that many of these ideas have already been envisioned within Tunes.org , LLVM , Microsoft's Singularity project, or in some other place that I haven't managed to discover or fully read, but I'm going to blog them anyway. Rather than wax philosophical, let me just dump out some ideas: Start with Minix 3. It's a new microkernel, and it's meant for real use, unlike the original Minix. "This new OS is extremely small, with the part that runs in kernel mode under 4000 lines of executable code.&quo

Haskell or Erlang?

I've coded in both Erlang and Haskell. Erlang is practical, efficient, and useful. It's got a wonderful niche in the distributed world, and it has some real success stories such as CouchDB and jabber.org. Haskell is elegant and beautiful. It's been successful in various programming language competitions. I have some experience in both, but I'm thinking it's time to really commit to learning one of them on a professional level. They both have good books out now, and it's probably time I read one of those books cover to cover. My question is which? Back in 2000, Perl had established a real niche for systems administration, CGI, and text processing. The syntax wasn't exactly beautiful (unless you're into that sort of thing), but it was popular and mature. Python hadn't really become popular, nor did it really have a strong niche (at least as far as I could see). I went with Python because of its elegance, but since then, I've coded both p