PyCharm 4.0.6 RC is available

Today we’ve published the PyCharm 4.0.6 RC bug-fix update.

This build has a few fixes that can be found in the release notes: a fix for the Django ORM inspection problem, a fix for the ManyToManyField resolve bug, a fix for an incremental search bug, a fix for HTML indentation broken when using Jinja tags, a fix for the “Nothing to show” bug in Structure View for Jinja2 HTML files, and fixes for a couple of platform bugs.

Download PyСharm 4.0.6 RC for your platform from the project EAP page and please report any bugs and feature request to our Issue Tracker. It also will be available shortly as a patch update from within the IDE. Make sure you’ve selected the Beta Releases channel in update settings.

Develop with Pleasure!
-PyCharm team

About Dmitry Filippov

Product Marketing Manager at JetBrains
This entry was posted in Early Access Preview. Bookmark the permalink.

11 Responses to PyCharm 4.0.6 RC is available

  1. Andrew says:

    I thought I was going insane with the HTML indentation issue. I’m excited to get this hotfix and see if it works. Thanks!

  2. alex says:

    i’m looking at my PyCharm and I can’t find were I can change update settings to enable the beta releases channel. help?

  3. Pingback: PyCharm 4.0.6 RC 发布 Python 集成开发环境 | 客家网络

  4. china liu says:

    Because I don’t understand English, please forgive me

    Whether in the next version of pycharm, handling the problem of Caton, look forward to the official reply!

  5. omfgnuts says:

    When hidpi support is coming?
    I’ve seen it in recent IDEA, any plans to implement it into PyCharm?

    • Dmitry Filippov says:

      Sure. The new hidpi support introduced in IDEA 14.1 is coming in PyCharm 4.1 (EAP starts on the next week)

  6. Tcab says:

    Great to see these early releases.
    But why no progress on a class A bug that has been around for many months re flicker when scrolling etc under Mac Yosemite. Hundreds of developers screaming in the forums for months

    • Dmitry Filippov says:

      Currently we’re working on it. Hopefully the fix comes to PyCharm before the PyCharm 4.5 final release.

Leave a Reply

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