Announcing the final PyCharm 3.1.2 release update

Happy Friday everyone!

Today we’re excited to announce the general availability of the PyCharm 3.1.2 update which is hopefully going to be the last release in PyCharm 3.1.x series!

Thanks everyone for giving us a lot of helpful feedback and reporting problems to our public tracker. You helped us a lot so we managed to fix a lot of problems. All fixes are applied to both free and open-source PyCharm Community Edition and advanced PyCharm Professional Edition with respect to supported functionality in these two editions. So as a recap, the most notable fixes in PyCharm 3.1.2 are: Django and JavaScript fixes, Nose test runner fixes, some fixes in code editor and in SQL support. Some problems with code navigation and in debugger for Python 3.4 are fixed as well. We also included a lot of performance enhancements into this release. For Mac users: we turned off native Mac message boxes by default to avoid UI locks. You can always turn them back on by setting in the configuration file.

You can review the complete list of changes here:
1. fixes between 3.1.1 and 3.1.2 RC
and here:
2. fixes between 3.1.2 RC and the final 3.1.2 release build.

The PyCharm 3.1.2 build is available for download, and you can also use the patch-based upgrade to upgrade from previous PyCharm versions without a full reinstallation.

And as for what’s coming up next – please stay tuned for the start of PyCharm 3.4 Early Access Preview program (EAP)!

Develop with pleasure!
-PyCharm team

About Dmitry Filippov

Product Marketing Manager at JetBrains
This entry was posted in Release Announcements. Bookmark the permalink.

4 Responses to Announcing the final PyCharm 3.1.2 release update

  1. Mathieson Facer says:

    Are there any updates on the send-to-Maya plugin? Been waiting for this for a long time.

  2. Kevin says:

    I’m not sure if this is an issue with the IntelliJ IDEA EAP, or whether it just doesn’t have all of the PyCharm support – but there does not appear to be an option to create a new Flask project with the 3.4.Beta.135.1 version of the Python plugin.

    • Kevin says:

      Seems I only had to go one step further in the menu!

      • Dmitry Filippov says:

        Ah, hope it works now! Previously we had such a problem with PyCharm 3.0 but eventually fixed it in 3.1. So the plugin should support the Flask + Python 3.4. Btw, old versions of Flask didn’t support Python 3.4 by themselves.

Leave a Reply

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