PyCharm 2016.1.1 EAP is available

It’s been a week since we released PyCharm 2016.1 and today we announce the early preview build of PyCharm 2016.1.1.

Some highlights of the PyCharm 2016.1.1 EAP build 145.597 are:

  • Supported Python versions changes
    • Dropped support for older Python versions before Python 3.5
    • Added preliminary support for Python 8
  • Various bug fixes
    • Fixed wrong indentation after copy-paste
    • Fixed generation of reStructuredText doc strings for methods with parameters
    • Fixed folding of custom regions

For the complete list of the changes see the release notes.

There’re other fixes that are currently under way and will hopefully get into the final PyCharm 2016.1.1 release. They’re: fixes for various Docker Compose support problems, a fix for extra libraries indexing. Stay tuned for further announcements.

We encourage you to give PyCharm 2016.1.1 EAP a try before its official release. Please change the updates channel to “Early Access Program” in the updates settings (Help|Check for updates…) to get the patch update to the EAP build from the recently released PyCharm 2016.1 or download the installer for your platform. Please report any bugs and feature request to our issue tracker.

-PyCharm team

About Dmitry Filippov

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

4 Responses to PyCharm 2016.1.1 EAP is available

  1. bughunter says:

    dropping supp … wait python 8 … what the hell … aaah, best april joke this year, really!

  2. Javier Tapia says:

    Python 8!!! “…to ensure that Python users suffer again with a new major release breaking all their legacy code.” LOL XD

  3. Shantanu says:

    Supported Python versions changes
    Dropped support for older Python versions before Python 3.5
    Added preliminary support for Python 8

    Haha.. Very funny.

  4. Rob van der Linde says:

    Nice, however the paste issue with the wrong indentation that was introduced in 2016.1 which has bugged me somewhat, has not been fixed with 2016.1.1, I am still experiencing it

Leave a Reply

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