The update includes a number of Django specific fixes and minor features, improvements for the debugger and some important fixes in the IDE platform. Check out the full release notes.

As usual, the new version is available for download from the JetBrains site.

And if you’re looking forward to new features and not just bugfixes, stay tuned — the Early Access for PyCharm 2.1 is coming soon!

So please download PyCharm 2.0.2 Release Candidate, check out the release notes, and let us know if anything goes wrong.

First of all, PyCharm currently supports Python versions starting with 2.4. This means that PyCharm’s own components written in Python use language features of Python 2.3 and 2.4, and simply will not run with Jython 2.2. With Jython 2.5, things like loading the list of library paths and completion for the standard library (which Giacomo had problems with) should work with no problems.

Second, it’s true that we do not support parsing jar files in PyCharm. When PyCharm was initially designed, the Java support in IntelliJ IDEA was a monolithic component, and we had the choice of either including it all or leaving it all out. Including it would mean that we would have a Python IDE that could do, say, an “Introduce Parameter” refactoring for Java but not for Python. Which would be really, really weird. So we decided to leave it all out.

On the other hand, the IntelliJ IDEA Python plugin can rely on the Java support in IntelliJ IDEA itself, and it contains all the necessary logic to support Java/Python interop. The plugin can resolve imports from Python files to Java code, perform cross-language refactorings, auto-import Java classes in Python code, etc. And as far as we know, it provides a better Jython development experience than any other IDE.

The good news is that, since that time, our Java support has become more modular, and now we have the option to include just enough of it in PyCharm to support Java/Python interop but not anything more. Therefore it’s possible that a future version of PyCharm will have the same degree of Jython support as the IntelliJ IDEA Python plugin currently has. However, we’re still not sure if there’s enough of a target audience for this functionality. So if you’d like to have this, please let us know.

If you’re using Windows or Linux, feel free to skip this update and wait for PyCharm 2.0.2.

We are very proud with this new release as it really takes PyCharm to the next level.
1. The range of supported technologies has expanded. The biggest addition is Mako and Jinja2 template languages. We’ve strengthened the core Python support by integrating code coverage, IPython, PyPy and some new static code analysis possibilities. Other big additions include support for Cython and CoffeeScript.

2. The new IDE UI makes PyCharm look much nicer on all supported platforms. Platform integration got much better with support for symbolic links, improved integration with docks, drag’n'drop between file manager and PyCharm on Linux and improvements on Mac OS X such as full-screen support.

3. Significantly reworked editor architecture provides better responsiveness and lag-less typing even in huge documents. Faster indexing and IDE startup speed are ensured on all supported platforms.

Read more about what else is new in PyCharm 2.0 and download the IDE now.

NOTE: PyCharm 2.0 is a free update for everyone who purchased their PyCharm license after Dec 12, 2010.

Develop with pleasure!
The PyCharm Team

• “Open in Browser” (Alt-F2) now works for Django templates. PyCharm tries to figure out the URL of the view in your application that renders this particular template, and to open that URL. If it fails, it simply opens the template as a static HTML file.
• The Move Statement action (Ctrl-Shift-Up/Down) has been rewritten and is much more reliable now.
• The Google App Engine integration now supports the Python 2.7 runtime added in Google App Engine 1.6.0.

The new version is available for download from the EAP page. As always, please submit your feedback to the issue tracker.

• Multiprocess debugging can now be enabled for any Python run configuration, not only for Django server (allowing to debug applications using Web frameworks like Flask, as well as many others);
• Added possibility to configure highlighting for function parameters, as well as a separate option for highlighting the ‘self’ parameter;
• Added keyboard shortcuts to jump to the beginning and end of an indented code block (Ctrl-[ and Ctrl-] in the default keymap);
• Move refactoring now works on Python packages correctly, updating the import statements referencing the package that has been moved;
• Project creation now works correctly with the development version of Django 1.4;
• Initial Python interpreter configuration on Mac OS X is now much faster thanks to the usage of pregenerated skeletons;
• PyCharm now recognizes the hashbang line in files with no extension and treats them as Python scripts if appropriate.

You can read the complete release notes or download PyCharm 2.0 Beta 2 from the EAP page. We’re very eager to hear your feedback and to resolve as many of the remaining issues as possible before the final 2.0 release.

The new major release adds support for coding in Cython, allows to use Mako and Jinja2 templates in your projects, enables you to check the test coverage of your code, allows opening multiple projects in one window, introduces JavaScript debugger, support for new and hot CoffeeScript language and many other big and small changes.

To get a full list of things coming in PyCharm 2.0 and download the Beta, check out the 2.0 Beta page on PyCharm web site.

We’re still hungry for more feedback to make PyCharm 2.0 even better by the time of the final release.

Develop with pleasure!
The PyCharm Team

• When opening a project, you now have an option to add it to the projects already open in the current window;



• The JavaScript debugger is now included in the PyCharm distribution and integrated with the Django server run configuration;



• The Python and Django consoles now support customization, including the possibility to specify a script which is automatically executed when the console is opened;

You can download the new build and check out the full release notes on the EAP page.

And now that the build is out, I can finally go home and get back to my game of Skyrim.

We are currently working on Cython support in PyCharm. Here is an overview of what’s already available in the EAP builds.

First of all, you get Cython syntax highlighting and error checking:

Next, there is context-sensitive code completion for Cython keywords, fields of structs, and attributes of extension types:

We will continue working on code completion for other elements, such as type names.

You can go to definitions and find usages of Cython cdef variables, functions, structs, and extension types. This is especially useful if you take into account various ways of importing Cython files, such as include statements and implicit imports of Cython definition files:

We have also adapted some Python inspections and refactorings for Cython. For example, PyCharm will highlight unresolved references in your Cython code:

There are various ways of compiling Cython modules: setup.py with Cython functions for distutils, Makefiles that directly call the cython compiler, etc. In PyCharm you can set up any external tool for compiling your Cython code from the IDE:

You can also set up the go to error line functionality via output filters for external tools:

Cython support in PyCharm is still work in progress. More Cython-related features and improvements will be available in PyCharm 2.0 EAP builds in the coming weeks.