PyCharm 2017.2 EAP 2 (build 172.2656.2)

Posted on by Dmitry Filippov

On this first summer day of 2017, we bring you the fresh PyCharm 2017.2 EAP build 172.2656. Since the previous EAP build, we’ve introduced a couple of new features as well as a lot of bug fixes:

– A new option for selecting PyQt backend while debugging
– A new string format inspection for new-style format methods
– Fixes for false positive Python inspections
– Fixes for unit testing support
– Jupiter Notebook support fixes
– And much more, see the release notes

>>>
# TODO:
# 1. Get the fresh PyCharm 2017.2 EAP build now from our website!
# 2. Participate in PyCharm 2017.2 EAP contest: File bugs, feature
# requests, participate in active discussions and win! Read more
# in the EAP announcement.

-PyCharm Team
The Drive to Develop

Comments below can no longer be edited.

3 Responses to PyCharm 2017.2 EAP 2 (build 172.2656.2)

  1. Kelly says:

    June 1, 2017

    What is “PyQt backend while debugging”? Why would one want to use that?

    • Ernst Haagsman says:

      June 6, 2017

      PyQT is a way to create desktop applications using a Qt frontend, learn more here: https://wiki.python.org/moin/PyQt

      With this improvement, it became easier to debug applications that use PyQT using PyCharm.

  2. Alon Diamant says:

    June 6, 2017

    What about this infuriating issue?
    Can we please solve it already?
    https://youtrack.jetbrains.com/issue/PY-22272

Subscribe

Subscribe for updates