Announcing General Availability of PyCharm 2016.1

Today we bring you PyCharm 2016.1, now available for download. This is the first 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.

PyCharmPro2016_1_splash@2x

As usual PyCharm 2016.1 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:

  • Python 2 and Python 3 type hinting and compatibility inspection
  • Docker Compose and Docker container settings
  • Tox Support
  • Improved Support for Django Forms
  • Significant debugger improvements
  • Enhanced support for IPython Notebook

Platform enhancements:

  • Git Rebase and Rename
  • Git Worktree Support
  • By-word changes highlighting in Diff Viewer
  • Enhanced Database Tools
  • Local Terminal Improvements

Web development improvements:

  • Improvements in ECMAScript 6 and TypeScript support
  • Major enhancements in Angular 2 support
  • Support for debugging asynchronous client-side code
  • Running and debugging Node.js apps on remote hosts
  • And even more

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

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

New versioning
As we announced earlier, with this release we’re changing the versioning scheme and moving away from one “major” release per year to several “equal” releases per year. Also, we’re aligning releases and version numbers across all products under JetBrains Toolbox. The new versioning will follow the format “YYYY.R” where yyyy represents the year, and “r” the release within that year.

The JetBrains Team
The Drive to Develop

About Dmitry Filippov

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

43 Responses to Announcing General Availability of PyCharm 2016.1

  1. Roy says:

    Is there no patch update from 5.0.4?

    • Dmitry Filippov says:

      No we don’t provide the patch between these two major versions. This is done for security reasons. It’s recommended to install v2016.1 along 5.0.4, then import settings and preferences and after than delete the previous installation.

      • Evgeny says:

        What about 5.1 RC?
        I have build 145.260 installed, but I don’t see the patch-update button.

        • Dmitry Filippov says:

          145.260 is the release build. Last RC was 145.259 patches should be already available.

          • Evgeny says:

            Oh, my bad, I was looking at the wrong number.
            I have 145.258, and as I said, I don’t see the patch button.

          • Evgeny says:

            So could you please tell how to update from Release Candidate to Release without a complete reinstall?

        • Andrey Vlasovskikh says:

          Currently we have patch updates only between consecutive builds, so you can update PyCharm 2016.1 RC -> 2016.1 RC2 -> 2016.1, but since RC2 was out it had become impossible to update from RC to 2016.1, sorry about that. We will make our patch update process more flexible.

          • Evgeny says:

            Well, that’s very unfortunate. Because I tried to update to RC2 as soon, as I read the blog post, but it wasn’t available at that time. And PyCharm actually never notified me about RC2. Then few days later, when I tried to update again, I got a notification that Release is available, but now I am unable to update to it without a full installation. It would be really great if you could store at least one or two previous patch updates on the server in order to prevent similar situations from happening.

  2. Roy says:

    The lack of patch updates between versions makes it difficult to keep upgrading a portable instance of PyCharm.

  3. Krzysztof Szumny says:

    FYI: I still have a problem with debugging inside docker, which I reported to RC2:

    http://blog.jetbrains.com/pycharm/2016/03/pycharm-2016-1-rc2-is-available/#comment-276031

    Anyone else have similar issues?

  4. Eli Bradley says:

    Is there going to be a PyCharm Edu 2016.1 release?

    • Dmitry Trofimov says:

      Hi Eli,
      we are planning to release a new version of PyCharm Edu in the late summer/early fall 2016.

      • Eli says:

        That’s in the 2016.2 release time-frame, according to the IDEA 2016.2 EAP homepage, correct? If it ends up being version 2016.2, will PyCharm Edu skip any more JetBrains Toolbox releases after 2016.1?

        Thanks,
        Eli

        • Dmitry Filippov says:

          Hi Eli,
          PyCharm Edu is the separate open-source project from PyCharm. It has different release cycle. And it’s not the part of JetBrains Toolbox. At the time of it’s next release the platfrom version is going to be 2016.2 indeed, that means PyCharm Edu next version will be based on the newest platform, however currently there’re no plans to change it’s versioning model.

  5. Pingback: Pycharm 2016.1 发布了 – 河间

  6. Serge says:

    Hate to said that, but after upgrade PyCharm is not usable for me anymore. On my os x 10.11.4 system clipboard is ignored, I cannot copy anything into / from PyCharm. And I need this functionality all the time. Unfortunately I overwritten previous version, which worked properly and am not sure how to roll back now. :(

    ps. I reported an issue in https://youtrack.jetbrains.com/issue/IDEA-143603 , but am not sure if it is correct bug.

  7. gelin yan says:

    after upgraded to pycharm 2016-1, I can’t use generating function comments by opening triple quotes and pressing Enter key. only intention action works.

    There is no problem with pycharm 5.0.2.

  8. Ethan Sherbondy says:

    I’m still running into issues with the docker-compose support.
    I have a compose file name development.yml which I use for local testing.
    The configuration in this file has a service named “webdev” which extends
    the “web” service from my docker-compose.yml file.

    I tried using the development.yml file as my configuration source and set the service name to the “webdev service”, upon which I got the following error:

    “Service must contain either build or image property: webdev”

    Is support for the “extends” syntax in docker files a bit off possibly?

    Really looking forward to using this functionality!

  9. Kunal says:

    Docker and compose do not seem to be working at all. I just keep getting this:
    Error:Unable to find support for com.jetbrains.python.remote.PyRemoteSdkAdditionalData@69e25234 SDK

    PyCharm 2016.1
    Build #PY-145.260, built on March 22, 2016
    JRE: 1.8.0_40-release-b132 x86_64
    JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o

    So basically it’s just an editor for me now..

  10. Niels says:

    Downloaded it, did a clean install on windows, but the “docker-compose” option as shown here: https://www.jetbrains.com/pycharm/whatsnew/#docker-compose never shows up for me.

    Regular docker containers will work, also i do have the “Docker container settings” option for run configurations, just no compose support.

    Is it a limitation of running pycharm in windows ?

  11. John says:

    Could you confirm the 2016.1 Linux community version download link works? I keep getting download errors. Thanks.

  12. Jonathan says:

    I upgraded PyCharm to the latest version and I am using with Mercurial for my project. Everytime I commit, PyCharm does not update the “changes” in the opened files. I have to restart it to refresh the files.

  13. liel says:

    hello the pycharm team. I have a professional license to pycharm 5.04, if i upgrade to pycharm 2016 do i lost my license from pycharm 5.04?
    by the way im on Linux mint 17.3
    thank you

    • Dmitry Filippov says:

      If you bought your license before Nov 2, 2015 you have the perpetual license for all the versions released within a year starting from the purchase date. If you bought your license after Nov 2, 2015 you have the subscription based license (perpetual fallback license for the released version on the day of your purchase and you can update to all new versions within a validity of your subscription). So the answer to your initial question: You don’t loose the license updating to new versions. You can always fall back.

      • Rifki says:

        Hi,
        By “fallback” do you mean that once my subscription expires I have to re-install the older PyCharm version (e.g. 5.0.4) to have pro features? If that is the case do you make available the older versions for download?

        • Dmitry Filippov says:

          If you buy the annual subscription, you get the perpetual fallback license for the currently released version. At the moment it’s PyCharm 2016.1. You’ll also get the perpetual license for all the minor bug updates within this version e.g. 2016.1.x.
          Within one year (the validity of your subscription) you can upgrade to any new versions 2016.x and use them at no charge. However when your subscription expires, you either might want to prolong your subscription and get a new fallback license, or you have to get back to the previous version for which you have the fallback license (2016.1.x).
          We do make available previous versions for download. You can find the link to the builds on the download page: https://www.jetbrains.com/pycharm/download/
          you can find the “Previous versions” link in there, which leads to the “Previous PyCharm releases” page:
          https://confluence.jetbrains.com/display/PYH/Previous+PyCharm+Releases
          Hope this answers your question. Let me know if there’s anything else I can help you with.

          • Rifki says:

            Thanks for clearing that out. I have one more question, Since I purchased my annual license before Nov 2, 2015 for PyCharm 5.0.x, does that mean I can continue to use 2016.1.x and don’t have to fallback to 5.0.x when my subscription expires? I just want to know what is the latest fallback I can use in case my subscription expires. Of course I’m talking about the PRO version here.

  14. Claire says:

    Just tried this latest version, used over 100% cpu when practically idle, had to reinstall Pycharm 5.

  15. Barry says:

    The tox support does not work with nosegae…:(

  16. Pingback: PyCharm 2016.1.1 EAP is available | PyCharm Blog

  17. Facundo.R says:

    No existe un diccionario en español? solo el corrector

Leave a Reply to Ethan Sherbondy Cancel reply

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