PyCharm 2.0.2 Release Candidate

It’s been more than a month since the previous PyCharm update, and although the team is working actively on PyCharm 2.1, we’ve got a bunch of bugfixes for 2.0 as well, both in the platform and in the PyCharm specific code. To make sure we’ve got everything right, we’re releasing the update as Early Access Preview first, and if no major problems are discovered, will release a production 2.0.2 update next week.

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

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

12 Responses to PyCharm 2.0.2 Release Candidate

  1. Greg says:

    It looks like PyCharm 2.0.1′s auto updater notices that there’s an update, but there’s no way to apply the update. Java 1.7.0 64-bit on Arch Linux.

  2. Joe White says:

    No CoffeeScript fixes?

    • Dmitry Jemerov says:

      This build does include a number of CoffeeScript fixes backported from the master branch; unfortunately they didn’t get listed in the release notes.

      • Joe White says:

        Weird. Some of the CoffeeScript bugs that are marked as “fixed” did make it into this version, but others did not.

        Is it likely that you’ll be able to merge the fix for RUBY-10241 before you ship? It was marked as “Duplicate” in YouTrack on 19 Jan, with a note claiming it was already fixed and would be in the next build of PyCharm, but the bug is still easily reproducible in this new build, using the original steps in YouTrack. This bug makes the code-formatting feature basically unusable, so it’d be great if you could get that fix in.

        It’d also be nice if the newly-introduced PY-5602 (actually just looks like an incomplete / poorly-coded fix for RUBY-10199) could get fixed too, but that may be asking for too much if you’re trying to rush this “release candidate” out after only one EAP build…

        • Dmitry Jemerov says:

          Joe,
          As of now, all of the CoffeeScript changes and fixes have been backported into the PyCharm 2.0.2 branch. We’re considering releasing one more RC build before the final release, to make sure nothing is broken there.

  3. 2.0.1 seems to have absolutely tanked performance on my laptop and this new update doesn’t seem to fix it.

    When I run my work project on 1.5.4 my computer functions fine, but when I try with 2.0.1 it brings my laptop to it’s knees with CPU usage. (I’m using an i7 processor with 6GB of memory on this laptop.)

    Any hints on what I should do to try to gather information about this problem?

Leave a Reply

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

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>