PyCharm 1.0 Roadmap Uncovered

Have you tried JetBrains Python IDE already? Then, you are probably interested what will be in PyCharm 1.0. Many are interested. So, here is our current vision.

The focus of PyCharm development leading to the 1.0 release will be less on major new features and more on ensuring that the existing functionality works great in different kinds of projects. However, there are a number of features that will definitely be added before the 1.0 release. They are:

  • Integrated REPL with syntax highlighting and code completion
  • Improved type system (tracking of method return types, tracking of collection content types)
  • IronPython support
  • Google App Engine support
  • Highlighting of unused import statements and Optimize Imports
  • Whole-project completion (completion of not imported classes and functions, with automatic addition of import statements)
  • More Python code inspections (e.g. pylint/pyflakes)

There are also some things we are considering, such as

  • Bundling Mercurial VCS support. It is now available as a third-party plugin
  • Support for additional template languages (Genshi, Mako)
  • Support for completion and resolve of .NET types in IronPython projects
  • Syntax highlighting, code completion and test runner for doctests

If you think some of these are really important for your work, add requests to PyCharm issue tracker. Of find an existing one and vote for it.

This is our current vision but it may change as time goes. You can influence changes as well — try PyCharm Early Access version, share your thoughts on PyCharm forum and vote for issues in PyCharm bug tracker.

The PyCharm roadmap is available at and you can watch this page for changes.

Develop with pleasure!
JetBrains Team

This entry was posted in Cool Feature, Early Access Preview. Bookmark the permalink.

8 Responses to PyCharm 1.0 Roadmap Uncovered

  1. PyCharm is starting to look really good!

    For me personally, from your list, the hot items are:

    * IronPython support
    * pyflakes and mercurial integration
    * better completion
    * Integrated REPL

  2. Attila says:

    Yeah! Do that, that will rock so much!!
    It’s such a shame that Django does not have the same ecosystem as Rails has. (Rails has at least 4 very advanced ides, including rubymine, whereas everything for Django is under development).
    So that’s probably the best thing that’s going to happen to Django in 2010! Keep it up, PyCharms approach is great! Thumbs up.

  3. Lennart Regebro says:

    Maybe I would be interested f you told me what it is. πŸ˜‰

    This is the standard error of bloggers blogging about software, they assume all their readers know what they are talking about. I do that too, sometimes.

    • yole says:


      Well, this is a post in a product blog, and it doesn’t really make sense to give a full description of the product in each and every post, does it?

  4. Eugene Wee says:

    Please consider bundling support for the Bazaar VCS. After asking around in the forum, I tried the Bzr4Intellij plugin, and although it was usable to some extent, it is lacking in some rather essential features. Without proper VCS integration, an IDE like PyCharm feels crippled.

    One direction that may be possible to take is to leverage the QBzr plugin. This is what the QBzr-Eclipse plugin for Eclipse has done. Unfortunately, this means that the interface provided does not blend in perfectly with the rest of the IDE, but I’ll take that any day for a feature set that is very usable (and the interface is familiar to those already using QBzr and/or QBzr-Eclipse).

    • yole says:


      Unfortunately we cannot use the Qt based plugin because it’s not possible to integrate Swing and Qt UIs cleanly. We’ll have to develop our own plugin, either starting from scratch or building upon Bzr4Intellij. However, it doesn’t look like we’ll have the resources for that until at least the second half of 2010.

  5. Pablo says:

    I really really want Mako support πŸ˜€

    I love pycharm.

  6. Eugene Toporov says:

    Pablo, please vote for Mako support in our issue-tracker:

Leave a Reply

Your email address will not be published. Required fields are marked *