Announcing General Availability of PyCharm 2016.2

Today we bring you PyCharm 2016.2, now available for download. This is the second update in the series of releases planned for 2016. Its outstanding new features for professional Python, Web and scientific development work together smoothly to offer you a unique coding experience.

PyCharm_splash20162

As usual, PyCharm 2016.2 is available as a full-featured Professional Edition for Python and Web development, or as a free and open-source Community Edition for pure Python and scientific development.

Here are some notable highlights of this release.

Python-related improvements:

  • vmprof Profiler Support
  • Pandas dataframes viewer
  • Thread suspend option
  • Function return values in the debugger
  • Improvements for package installation from requirements.txt
  • Configuration for optimize imports
  • Enhanced postfix code completion
  • Lettuce scenario outlines

Platform enhancements:

  • Support for ligatures
  • Improved inspection tool
  • Custom background image for the editor
  • Regex support improvement
  • Handling of unversioned files
  • Improvements in working with patches
  • Enhanced VCS Log Viewer
  • Database tool improvements
  • And even more

For more details please watch this short What’s New in PyCharm 2016.2 video:

Read more about what’s new in PyCharm 2016.2 on the product website and download the IDE for your platform.

Your JetBrains Team
The Drive to Develop

About Dmitry Filippov

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

14 Responses to Announcing General Availability of PyCharm 2016.2

  1. Evgeny says:

    Hi,

    I’ve got a notification from PyCharm to download the new version, but I don’t see the option to download the update patch. I know that normally you would say to wait until it appears. However, isn’t it a bit strange that a customer gets a notification within an alreay installed Idea/PyCharm to download a new version with no patch available, while I suspect that most of the user prefer the update patch method. Could you please upload patches earlier or at least add an option “Don’t notify about updates until the patch is available”.
    Thanks!

    • Dario Varotto says:

      With major releases you won’t have patch updates.
      Just download the new version, run it and enjoy the new features.

      • Evgeny says:

        Yeah, I agree that for major releases it’s safer to do a full install.
        However, I am currently on 2016.1.4, and 2016.2 doesn’t look like a major version change to me. Or have the versioning schema been changed, so that now upgrade from xxxx.y to xxxx.z is also considered a major version change? If so, then it’s very confusing, as in many projects releases are versioned as major_version.minor_version.build/patch_version

        PS:
        Still waiting for the patch-update button to appear….

        • Dmitry Filippov says:

          2016.2 is the next major version. While this versioning schema may seem confusing, this is kind of a standard. It’s different from classic major.minor.update. It’s now year.release_number_in_year.update we do several releases per year, so the difference between 2016.3 and 2017.1 can be much smaller than between 2016.1 and 2016.2.
          2016.2 has different, hugely upgraded platform, so it’s not easy to upgrade to it with a patch. It’s not only safer and more reliable, it’s also faster to install the new version from scratch. You can install it along with an old version and try how it works for your projects. If it has some bugs, you won’t loose your previous working version. PyCharm is the professional tool, so we do care a lot about safety and reliability.

          • Evgeny says:

            If it’s a major release, than I totally agree that it’s better to perform a full installation. Thanks a lot for the clarification.
            I was just confused by the versioning schema, and it wasn’t mentioned anywhere that it’s a major release – neither in the popup window in PyCharm nor in the blog post. Btw, even the blog post says “This is the second update” – I guess that was another reason I thought it was a minor update. I guess having small note in PyCharm’s popup window like “Note: this is a major release, only full installation is available” would also help.

    • Kristof says:

      II agree with Evgeny. An option to go to the main download page confuses the users. An in-app update is what we want :-).

      Waiting a bit more.

      • Dmitry Filippov says:

        What would you do if the next new version have some serious bugs that will stop you from working on your current projects? It’s suggested that developers install new major versions from scratch along with their current installations.

  2. Bach says:

    Another thing you should do is migrate licenses when updating. You ask again for the license info after upgrade. If the old one is valid, why not just apply it?

  3. Dmitry Filippov says:

    Installing new major version is like installing a new PyCharm instance. You have to login into it. Providing your license is very easy: you just need to login with your JetBrains account credentials.

  4. Ken White says:

    The Pandas DataFrame viewer is a very welcome addition. Unfortunately, the implementation seems rushed and it is still inferior to the one in Spyder: there is no button to automatically resize the columns, and I couldn’t get the floating-point formatting to work. (Dragging to change the column widths one-by-one is comparatively slow and awkward.)

    I also got a scary-looking error when I attempted to change the name of the variable being displayed (Guarded Block Modification Attempt, and then “waiting for process to detach at bottom of screen”).

    Is there some way to configure the viewer so I can set a default value for the color option and the floating-point format? Thanks again for adding this feature — with some improvements it may allow me to stop using Spyder.

    • Dmitry Trofimov says:

      Ken, thanks for the feedback. We are going to improve this viewer in the next PyCharm update. Could you please submit your bug report and requests about usability of the view directly to our issue tracker: youtrack.jetbrains.com/issues/PY

      Currently there is no way to set a default value for the color option and floating-point format.

  5. Paul says:

    This update brought back my favourite “bug”. I work on a case sensitive disk and had properly altered the idea.properties file on my mac in
    /Users/xxx/Library/Preferences/

    But this doesn’t seem to do the trick anymore, which means I had to alter the idea.properties directly in the application, which made me break the “code signature” causing my os to ask me to allow pycharm acces each time I load it. Aaaargggg.

    Solutions?

    ps. Love the pandas DataFrame viewer.

  6. dave says:

    crazy high cpu usage on mac :-(

Leave a Reply to Evgeny Cancel reply

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