Discover PyCharm 3.4 future plans

Yes it’s that time again! We’re eager to share our future plans for PyCharm 3.4, the upcoming update of our most intelligent Python IDE, to start off the discussion and of course get your valuable feedback.

The release theme is going to be “User experience and performance improvements“. PyCharm 3.4 is planned for release in April – May 2014. The roadmap is neither a finalized list of tasks to be implemented in PyCharm 3.4 nor a promise to include everything into the upcoming release. The roadmap is flexible, so we can probably add or remove something from the list.

We’re starting PyCharm 3.4 Early Access Program as soon as we are ready to show you something from the new feature set. So stay tuned and file your requests or wishes to our Public Tracker meanwhile.

The most noteworthy things from the current PyCharm 3.4 Roadmap include:

–  A number of performance improvements in different parts of PyCharm
– A bunch of usability improvements like temporary buffer for editing, Python live templates and new project wizard
–  Django 1.7 support
–  Improvements of remote development features
–  Debugger impovements
–  and a lot more…

In planning this release we decided to focus on performance optimizations and usability improvements, putting emphasis on delivering even more fast and steady solutions for your development needs.
We really hope you’ll enjoy these new improvements coming soon in PyCharm 3.4. If you have any comments, suggestions or queries, please feel free to share them right here in our blog or post them to our or Discussion Forum. Also, follow us on Twitter @pycharm to stay tuned to the latest PyCharm news.

Develop with Pleasure!
PyCharm Team

About Dmitry Filippov

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

39 Responses to Discover PyCharm 3.4 future plans

  1. The ability to debug remote subprocesses would be incredibly useful for me and our team.

    Would like to see PY-11761 fixed as it’s pretty destructive.

    Sharing improvements would be great, like sharing external & remote external tools. Perhaps some sort of centralized sharing dashboard would be nice too so you could manage that all at once.

    Honestly not too concerned about performance; PyCharm is not especially slow for me. Takes a little while to load up initially but if you don’t exit PyCharm you rarely have that problem!

    • traff says:

      The ability to debug remote subprocesses is already supported. If it doesn’t work for you, please submit an issue, describing the problem.

      By performance we mean not only speed, but also memory consumption – and there are some places where it could be more optimal.

  2. Doug Rohm says:

    I take it the version change from 3.1.x to 3.4.x was to follow the upcoming release of Python 3.4.0? Support for that will be included?

  3. Sam says:


    Any news or ETA on the Maya plugin ?

    Thank you.

  4. Carl Bourne says:

    Will there be any support for Kivy?

  5. Jason Bennett says:

    A better REPL would be nice, especially one that autoreloaded from the editor.

    • traff says:

      We have plans to enhance the REPL, but there is no certain road map yet for that subsystem. Please vote for existing issues and submit new ones.

  6. ivan says:

    Any form designer for pyqt? Drag and Drop widget pyqt…

  7. Peter Smit says:

    I see “Remote interpreters” is on the top of the list. Could you maybe include PY-6247 (using native ssh?)

  8. Gaëtan de Menten says:

    Regarding performance, I have never had any issue, except from the debugger which is really sluggish at times. Not sure what triggers the slow down though, otherwise I would have created an issue. Strangely I have never had this issue when I was using the PyDev debugger within Eclipse (on which PyCharm’s debugger is apparently based).

    Sure, PyCharm starts up very slowly, but I personally couldn’t care less as it is open all day, every day.

  9. Yury V. Zaytsev says:

    I’m really happy with PyCharm 3.1.x releases, in terms of stability they by far surpass the 2.6.x / 2.7.x upgrades. Something I’m very much looking forward for are improvements to the static analysis engine, especially in what concerns NumPy / SciPy and better support for Cython syntax; to me, that’s what usability is all about :-)

    I’ve been tracking a bunch of NumPy / SciPy tickets, but eventually got discouraged by the lack of feedback. I came to realize that in some instances wrong analysis is because of lacking / improper docstrings, and in some instances more like due to PyCharm problems. However, in order to help you, I need your help, because I find it very hard to classify these issues. I’m happy to try pushing docstring changes into NumPy and maintaining skeletons when things have to be fixed on the PyCharm side.

    • traff says:

      Hi Yury! Thanks a lot for your feedback! It’s true, that NumPy/SciPy issue had lack of our attention in a few latest releases, but we are going to improve the situation in the field of scientific python, so stay tuned. And surely we’d like to collaborate.

    • Mike says:

      A very late +1 for better Numpy/Scipy support

  10. Jorge says:

    It would be great if when method gets called the editor suggest the named params automatically, similar to how wingide do it.

    • Dmitry Filippov says:

      Jorge, doesn’t PyCharm suggest them by default? Could you please give an example and what you expect from an IDE in this regard?

  11. Greg says:

    Looking forward to this!

  12. August says:

    I know performance is not as sexy as new features but optimizing this does pay off in terms of a nice “feel” over time. Looking forward to the developments.

  13. Rob says:

    Is support for Subversion 1.8 on the PyCharm 3.4 roadmap? If I need to submit a YouTrack ticket, please let me know.


  14. Peter Shinners says:

    With “Temporary Buffers” does that mean we could have the ‘charm’ command line tool read from stdin and create an in-memory buffer?

    echo "Hello Pycharm" | charm

  15. Johan De Messemaeker says:

    Official FreeBSD support?

    • Dmitry Filippov says:

      Unfortunately there will be no official support of FreeBSD) Just a couple of PyCharm users use FreeBSD. Seems to be not worth adding any additional support.

  16. DeeJay1 says:

    Support for Sublime style text selections like in IDEA 13.1 would be great 😉

  17. Jasper Clark says:

    I would like more support for using Vagrant to develop and debug… I prefer to run PyCharm on my host, and have multiple development VMs for different languages / projects.

    In version 3.4 adding the ability for a deployment server to use a Vagrant configuration rather then manually specifying the config would be nice

    I think the ability to have PyCharm’s project files themselves stored on Vagrant VM rather than reside on the host would be ideal. This would remove the necessity to “deploy” after every change, and allow a single instance of PyCharm to edit and manage various projects spread across disparate architectures.

  18. Paul Everitt says:

    WebStorm 8 has a bunch of platform improvements which I presume PyCharm 3.4 will get. It also has a number of web development features: AngularJS support, Grunt integration, etc.

    Are these planned for PyCharm 3.4?

    • Dmitry Filippov says:

      Hi Paul,

      Your assumption is correct. All platform improvements will go to PyCharm 3.4 as they are common across all our IDEs. All the new web development stuff will be available in PyCharm 3.4 under the same conditions as previously – PyCharm includes all the functionality of WebStorm either bundled inside PyCharm or it can be available as a separate plugin from official plugin repository at no charge. So for example we’ll probably bundle AngularJS, but Grunt support will be available through a free plugin.

  19. Hans Wurat says:

    Hi Pycharm team,

    This is good news :) I really enjoy working with PyCharm and found it very helpful in the past. However a capability to profile python scripts would be a great addition to the features you already have implemented (like the superb debugger). I’ve seen that Komodo has some sort of profiling, I would like to see something similar in PyCharm.

    Best regards and keep up the good work,

Leave a Reply

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