PyCharm 2017.2.2 is now available

After last week’s RC for PyCharm 2017.2.2 we have fixed some issues on the create new project screen. Get the new version from our website!

Improvements are in the following areas:

  • An issue in the creation of Angular CLI projects
  • Code insight and inspection fixes: “method may be static” issues, and misidentification of Python 3.7
  • Django: Cache conflict with Jinja template project, and Ctrl+Click on widget templates
  • Docker: Docker Compose environment variable issues
  • JavaScript: go to declaration, go to implementation
  • And much more, check out the release notes for details

We’d like to thank our users who have reported these bugs for helping us to resolve them! If you find a bug, please let us know on YouTrack.

If you use Django, but don’t have PyCharm Professional Edition yet, you may be interested to learn about our Django Software Foundation promotion. You can get a 30% discount on PyCharm, and support the Django Software Foundation at the same time.

-PyCharm Team
The Drive to Develop

This entry was posted in Release Announcements and tagged . Bookmark the permalink.

10 Responses to PyCharm 2017.2.2 is now available

  1. Pingback: PyCharm 2017.2.2 发布,Python IDE | News Pod

  2. Pingback: PyCharm 2017.2.2 发布,Python IDE – 技术成就梦想

  3. Umang Chamaria says:

    This version of IDE hangs on Mac Pro 8gb ram variant when you do a find in path.
    Please release a fix as soon as possible.
    The same worked fine in the previous version on the same machine, so definitely not a machine issue.
    Using a paid version of pycharm

  4. Gondalman says:

    The version doesn’t hang on my macbook pro but is definitively much slower than 2017.1. Please have a look at what happens inside. Thanks!

  5. Gloobee says:

    I apologize if this was asked many times before, but is there a reason why some updates to PyCharm don’t autoupdate (need to re-download from website)?

    • Ernst Haagsman says:

      We provide patch updates which are specifically to upgrade from a certain version to another specified version. If we don’t have a patch for the From-To version pair that you need, unfortunately, you will need to reinstall to update.

  6. Mehmet says:

    Ernst,
    Your answer to Gloobee’s question was not clear to me.

    • Ernst Haagsman says:

      Hi Mehmet,

      The in-place update, which updates your PyCharm without reinstalling, is always made for a specific version pair. So let’s say we just released PyCharm 2017.2.2, and also built an in-place update for PyCharm 2017.2.1->2017.2.2. That means that if you have 2017.2.1 installed, and you click ‘Update’, you won’t need to reinstall to get 2017.2.2. However, if you skipped a version, and you were still using 2017.2.0, our updater wouldn’t be able to find an update from 2017.2.0->2017.2.2. In that case, you would need to do a full reinstall.

      Please let me know if something is still unclear about it!

      • Me says:

        The unclarity is why not the updater just perform two successive in-place updates; this is surely faster than a full download and reinstall.

Leave a Reply

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