Announcing PyCharm 3.1.2 Release Candidate

Happy Friday everyone!

We are happy to announce the availability of the PyCharm 3.1.2 Release Candidate. Since the previous bugfix update of PyCharm 3.1, we’ve gathered a lot of fixes, enhancements and performance improvements in various PyCharm’s subsystems. We’re almost ready to release them to you as PyCharm 3.1.2, but before we do that, we’d like to make sure that the build is good enough and doesn’t contain any showstoppers. That’s why we’re releasing PyCharm 3.1.2 RC today.

Installers for PyCharm 3.1.2 RC (build 133.1143) can be found on Early Access Preview page.

The complete list of changes can be found here: PyCharm 3.1.2 RC release notes

Patch updates from previous versions should be available soon. Just make sure you’ve enabled the “Early Access Preview” update channel in your update settings. In case you want to keep your current PyCharm installation untouched, but still want to try new RC version, please don’t use patch update, but install the new version alongside from scratch.

We hope there will be no major bugs in this build so we’ll finally release it as PyCharm 3.1.2 on the next week.
As always, please report any problem you found to our public issue tracker. Thus you help us making PyCharm better.

Follow us on twitter to receive our latest news.

Develop with Pleasure!
-PyCharm team

About Dmitry Filippov

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

4 Responses to Announcing PyCharm 3.1.2 Release Candidate

  1. Omu says:

    Autoupdate on Linux doesn’t work. It sees the update, but after restart it’s still 3.1.1.

    Here is the terminal output:

    Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=350m; support was removed in 8.0
    [ 9887] WARN - api.vfs.impl.local.FileWatcher - Watcher terminated with exit code 0
    Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=350m; support was removed in 8.0
    Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/log4j/Layout
    at java.lang.Class.getDeclaredMethods0(Native Method)
    at java.lang.Class.privateGetDeclaredMethods(
    at java.lang.Class.getMethod0(
    at java.lang.Class.getMethod(
    at sun.launcher.LauncherHelper.validateMainClass(
    at sun.launcher.LauncherHelper.checkAndLoadMain(
    Caused by: java.lang.ClassNotFoundException: org.apache.log4j.Layout
    at Method)
    at java.lang.ClassLoader.loadClass(
    at sun.misc.Launcher$AppClassLoader.loadClass(
    at java.lang.ClassLoader.loadClass(
    ... 6 more
    Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=350m; support was removed in 8.0
    [ 36565] WARN - api.vfs.impl.local.FileWatcher - Watcher terminated with exit code 0

  2. David Ichim says:

    Has the pycharm team moved to work on other IDE’s from jetbrains?
    How awful is it that Idea get’s a new build for April Fools Day, and Pycharm didn’t even get the 3.1.2 release promised last week, let alone the 3.4 EAP that you keep saying it’s coming. Seriously I feel like Pycharm became a lost child, while everyone gets releases we get just empty promises :(

    • Dmitry Filippov says:

      Hi David,

      Your feedback is understandable. Well, that’s all because of a mix of some circumstances and that now we have a transition period between PyCharm 3.1 and 3.4 series so transition between development branches and so on. We have to transit our changes/fixes both PyCharm specific and platform specific across different branches – you know a lot of mess. That’s why no final 3.1 and still no EAP for 3.4 yet. Definitely it took us almost 2 weeks to finally release 3.1.2 – and we’ll definitely do it by the end of this week. 3.4 EAP is coming closely after the release of 3.1.2 as well (few days to finish with some things).
      So just please be patient.
      Btw, you can always track what’s going on PyCharm project with youtrack. See how many tickets have been resolved since 3.1.2 RC:
      So we are here, we’ve not lost =)

Leave a Reply

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