Skip to end of metadata
Go to start of metadata

PyCharm 3.1 Roadmap

Release date: beginning of 2014

  • Improve Vagrant (traff)
    • Support providers [PY-9854]
    • Support multiple configurations [PY-9994]
    • Install/Uninstall plugins
  • AppEngine (ktisha)
  • Python formatter consistency with PEP8 (traff)
  • Python 3.4 support (interpreter detection, enum and pathlib libraries) [PY-11677] (vlan)
  • Django 1.6 (ktisha)
  • Terminal tabs (split, move to editor) (traff)
  • More precise keywords completion [PY-10248, PY-4540, PY-3687, PY-4539] (ktisha)
  • String literals completion: identifiers (implemented for docstrings) [PY-2953] (ktisha)
  • Skeletons generation -> background [PY-6164] (vlan)
  • Default Python interpreter from PATH [PY-4733] (vlan)
  • Don't highlight errors without interpreter [PY-11589] (vlan)
  • Language injections for formatted and concatenated strings (vlan)
  • Performance optimizations (vlan, ktisha, traff)
    • Generator: Split big generated modules (like _Gtk, PyQt) into smaller ones [PY-11703] (ktisha)
    • Injected languages performance (vlan)
    • Highlight usages under caret performance (vlan)
    • Performance problems when editing large *.po files [PY-6662] (ktisha)
Platorm features available
  • New Git & Mercurial log
  • Support for Subversion 1.8
  • Lens Mode
  • Speed Search in Project View
  • Search Everywhere
Postponed to later releases
  • Python parser error recovery (vlan)
  • Missing quick-fixes  - quick fixes list needed
  • Scratch plugin [PY-3151] (vlan)
  • PTY in run configurations (traff)
    • needs redesign of Run configuration page
    • running processes with PTY was implemented in Vagrant support and seems to be not very stable - it's early to add it to run configurations
  • Goto symbol: resolve to modules and packages [PY-6923]
  • Unresolved/unused imports [PY-4330], unused/undefined variables
  • Python live-templates [PY-2378] (vlan)
  • Performance enhancements:
    • Terminal memory consumption (traff) - affects platform to much to be implemented in 3.1

Legend
  - Feature Implemented
  - Under Investigation
  - In Progress
  - Postponed

traff - Dmitry Trofimov (PyCharm team lead, developer)

ktisha - Ekaterina Tuzova (PyCharm developer)

vlan - Andrey Vlasovskikh (PyCharm developer)

Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Dec 04, 2013

    Is it possible to update this roadmap by community?  Me and my colleagues wait this feature very long time: http://youtrack.jetbrains.com/issue/PY-2887
    cprofile + runsnake inside pycharm can be killer feature.

    1. Dec 04, 2013

      Anton, profiler integration is not just another one feature. It will take a lot of time to make it working from IDE as you may expect (with integration to all other PyCharm tools). That's why we are not able to update this roadmap since there are other essential features to complete. However yeah, we know this feature is highly upvoted and it is what up on ours mind currently for the next release or two.

  2. Dec 20, 2013

    Is it possible to Pycharm 3.1 will work developing Flask Applications with Python 3.x? So far, when I created a new project -> Project type: "Flask project" and interpreter: "Python 3.3" PyCharm shows the message: "Flask is not supported for the selected interpreter".

    1. Dec 20, 2013

      Hi Danny,

      Yeah in previous versions PyCharm 3.0 Flask was not working with python 3.3 

      In PyCharm 3.1 EAP http://blog.jetbrains.com/pycharm/2013/12/announcing-the-pycharm-3-1-eap-opening/  it works. Here is the fixed bug: http://youtrack.jetbrains.com/issue/PY-10028

      There is still one bug for python 3.3+flask debugger http://youtrack.jetbrains.com/issue/PY-10535  but we definitely will fix it before 3.1