The Second Release Candidate for PyCharm 3.4 is now available

We are now approaching the final steps towards the PyCharm 3.4 release which is planned to be released in short. So today we’re happy to announce the availability of the second release candidate for PyCharm 3.4.

Generally speaking, feedback on the previous PyCharm 3.4 RC has been positive and we believe this second release candidate will be even better. That’s why we invite you all to try it out. Please take it for a spin and give us feedback. The PyCharm 3.4 RC2 build 135.973  is available for download from the Early Access Preview page.

The last few days since the announcement of PyCharm 3.4 RC, we’ve been only fixing bugs. So no any new functionality in this build. The complete list of bug fixes can be found in the Release Notes.

We hope that there will be no major bugs, but anyway, should you encounter any problems, please report them to our public tracker.

A patch update from the previous RC and EAP builds should be available soon.

Stay tuned, follow us on twitter and develop with pleasure!

-PyCharm team

About Dmitry Filippov

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

3 Responses to The Second Release Candidate for PyCharm 3.4 is now available

  1. Marcin says:

    Has something changed in Jinja2 support? I can’t use tab to expand jinja tags: I get HTML tags instead. For example before 3.4 I could write

    and PyCharm expanded it to

    jinja tag. Now I get

    .

  2. traff says:

    Hi Marcin, this is probably a regression. As a workaround you could add HTML file type as a context for Django live templates. Or it is possible to add {% before template name like {% for.

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 class="" title="" data-url=""> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <pre class="" title="" data-url=""> <span class="" title="" data-url="">