AppCode
CLion
DataGrip
GoLand
IntelliJ IDEA
MPS
PhpStorm
PyCharm
Rider
RubyMine
WebStorm
Toolbox App
.NET Tools
ReSharper C++
Space
TeamCity
Upsource
YouTrack
Datalore
Hub
Kotlin
Ktor
News
Team
JetBrains PlatformPyCharm 2017.1 Release Candidate
Great news: We are now approaching the final steps towards the first major release in 2017. So today we’ve published the PyCharm 2017.1 Release Candidate. Download it now from our early access page.
Since the previous early access preview build we’ve fixed a lot of bugs in various subsystems and also introduced some important improvements: details in the release notes.
In case you missed what’s new in upcoming PyCharm 2017.1, check out the early access page to learn about the features included in the new version. Some highlights:
- The Python debugger got forty times faster for Python 3.6 projects, and up to two times faster for older versions of Python
- Improved Python and JavaScript testing
- Support for the six library
- Zero-latency typing
- Support for native Docker for macOS
- And much more
We hope that there will be no major bugs in the RC build, however, should you encounter any problems, please report them to YouTrack – we’ll still have a bit of time to fix stuff before the final release.
Stay tuned for a PyCharm 2017.1 release announcement and follow us on Twitter.
-PyCharm team
me says:
March 17, 2017I do not feel there is such a big change for
forty times faster for Python 3.6 projects
I have pycharm 2016.3 and this version installed, the debug start time seems to be the same. And runtime is also the same. Is it because my project is small?
Dmitry Filippov says:
March 17, 2017I believe yes, the possible reason you don’t see a difference is that your project is small.
Shortly after release we’re going to publish an interview blog post with a developer implemented those speedups explaining everything in details. Like which cases are affected or not.
Andrzej says:
March 17, 2017Wasn’t zero latency typing available before by using editor.zero.latency.typing=true in idea.properties file?
Dmitry Filippov says:
March 17, 2017Yes it was available before using the change to idea.properties. The zero latency typing has proved to be efficient so now we enable it by default. The feature itself got some fixes an improvements.
Ruslan says:
March 17, 2017Do you have a plan enable time tracker plugin in PyCharm?
https://www.jetbrains.com/help/idea/2016.3/time-tracking-tool-window.html
Andrey Vlasovskikh says:
March 17, 2017We will consider the time tracking plugin for inclusion in our next versions. Feel free to vote for this feature request.
PyCharm 2016.3.3 Released | PyCharm Blog says:
March 17, 2017[…] ← PyCharm 2017.1 Release Candidate […]
PyCharm: PyCharm 2016.3.3 Released | Adrian Tudor Web Designer and Programmer says:
March 17, 2017[…] after announcing PyCharm 2017.1 Release Candidate today we bring you some important backport fixes for the current PyCharm stable version. Please […]
Wassim Seifeddine says:
March 22, 2017If i have a running docker container and i want to use in the latest version of pycharm. Can i configure my project to use the currently install python interpreter that is already installed in the running docker container? it seems that i have run a new container so that this will work
Thanks
VK says:
March 22, 2017Hello!
Please see this article, the Linux section of the article.
Selecting the JDK version the IDE will run under
https://intellij-support.jetbrains.com/hc/en-us/articles/206544879
— Updated Today at 14:23 (today means 2017-03-22 at the time of submit of my comment)
My question:
Does this already apply to Linux version of the PyCharm? Does the PyCharm for Linux already get shipped with the bundled custom version of the JRE? If yes, from which version? If not, will this happen anytime soon?
Ernst Haagsman says:
March 22, 2017PyCharm for Linux has shipped with the custom JRE for several versions already, if you’re on a 2016 version you’re very likely using the custom JRE.
VK says:
March 23, 2017@ Ernst Haagsman: Thanks for your reply.
One last question: Would it be possible to download the 32-bit build of the customized JRE?