PyCharm: Py is for Python, Charm is about the IDE

You are reading the blog of JetBrains PyCharm, the new Integrated Development Environment (IDE) for programming in Python.

We’ve been working on the Python plugin for IntelliJ IDEA, our flagship Java IDE, for some time and we will continue supporting it making IntelliJ IDEA a better environment for polyglot developers. But our recent success with IDEs for Ruby/Rails (RubyMine) and for Web/PHP (Web IDE) tells us that an IDE for Python will be in demand as well.

Therefore, please welcome the new product from JetBrains — PyCharm, environment for Python developers and web developers working with Django.

PyCharm is currently available as Public Preview, and the version 1.0 release is planned for mid-2010. We very much value user feedback and look forward to your ideas and suggestions on PyCharm Discussion forum and in Issue tracker.

Make sure you subscribe to this blog RSS to be notified about EAP updates, new releases and interesting facts about PyCharm IDE, or follow @PyCharm on Twitter.

Oops, it seems that WordPress likes eating less-than signs as if it was html.Anything that’d run somothly with 256 MB of memory? I use Emacs most of the time, but it’s far from The Best Damn Python Enabled IDE Ever Period(tm)

Looks pretty cool but after downloading it and trying a couple things can I make a request? It doesn’t appear to be very Virtualenv friendly and (at least I haven’t figure out where yet) I can’t configure a run/test environment.

I see where I can point to/configure alternative interpreter versions, but I need to point to specific env’s. In Eclipse-PyDev I can both customize the interpreter and the PythonPath as well as configure custom run/debug operations.

Mercurial support is currently available as a third-party plugin. We’re evaluating the possibility to support it in the 1.0 release as a bundled plugin.

Brian,

Virtualenv support has already been implemented and will be included in the next EAP build. As for the Web frameworks, we’re focusing only on Django for 1.0 (there’s still lots of work to do in that area), but it’s likely that we’ll add support for other frameworks in future versions.