PyCharm 5.0.2 EAP is Available

Posted on by Dmitry Filippov

It’s been a while since we released PyCharm 5 and today we announce the early preview build of PyCharm 5.0.2. The list of bug fixes and improvements for this build can be found here.

Some highlights of the PyCharm 5.0.2 build 143.869.1 are:

  • fixes for different performance issues
  • a fix for Google docstrings support (PY-17220)
  • a fix for code completion not working in IPython Notebook (PY-16392)
  • a number of fixes for Docker support
  • fixes for integrated test runner
  • a few fixes for Django support
  • and much more

Please give PyCharm 5.0.2 EAP a try before its official release and please report any bugs and feature request to our issue tracker.

Develop with Pleasure!
-PyCharm team

Comments below can no longer be edited.

8 Responses to PyCharm 5.0.2 EAP is Available

  1. Christopher Hiller says:

    November 18, 2015

    Dmitry,

    Running “Check for Updates…” from PyCharm 5.0.1 finds nothing; is this intended?

    • Dmitry Filippov says:

      November 19, 2015

      Should work now.

  2. Dustin says:

    November 19, 2015

    The link to the list of bug fixes and improvements leads me to a youtrack search page that says:

    Oops! Something went wrong with your search request.
    Can’t find value: “5.0.2 143.869.1”.

    • Dmitry Filippov says:

      November 19, 2015

      thanks for pointing out. Fixed.

  3. Raj says:

    November 21, 2015

    After installing PyCharm 5.0.2 Community Edition EAP (build 143.869.1, November 18, 2015) I do not find Django and other framework.

    • Dmitry Filippov says:

      November 23, 2015

      Django is supported only in PyCharm Professional Edition

  4. Kiran says:

    November 21, 2015

    Too bad that one the coolest features is currently still broken and has been since the release of 5.0. There have been several different issues centered around this feature and it’s still not fixed. The latest I could find: https://youtrack.jetbrains.com/issue/PY-17722

    • Dmitry Filippov says:

      November 23, 2015

      we’re working on this bug

Subscribe

Subscribe for updates