Since the release of the first EAP build two weeks ago, the PyCharm team has been busy cranking out features for the new 2.0 version. Not all of the stuff that’s been cooking is ready for release just yet, but the list of stuff that went into the new build is quite impressive nevertheless:
- Initial support for Jinja2 templates (work in progress)
- Many improvements for Mako templates: code completion, typing assistance, comment code shortcut, navigation and much more
- Smart Step Into action in the debugger, allowing you to select the call to step into when the current line contains multiple method calls
- Goto Test action, allowing you to quickly navigate from a class to its test and back.
You can download the new build and read the detailed release notes on the EAP page.
And what’s coming up in the next weeks? Two big new features, both with names that happen to start with the letter “C”. 
And remember that the 50% discount on personal licenses is valid until the end of September. All licenses purchases now will qualify for a free upgrade to PyCharm 2.0 when the final version is released.
Will there be an EAP for the python plugin so that it will work with the Intellij 11 EAP? Ot at least an update to the current plugin so it uses the new API so I can run the old plugin with the Intellij 11 EAP? Really excited for this update!
There will definitely be no update of the current plugin to the new API. As for releasing EAP builds of the new plugin, I think that’s possible, but I can’t promise that there will be a matching plugin release for every IDEA 11 EAP build.
Thanks for the reply Dmitry! I can see how it would be difficult to track the changing API’s of the EAP build. Just thought it couldn’t hurt to ask. I know in the past I haven’t been able to use the Python plugin during the Intellij EAP, so no surprise there. Thanks again and great work on PyCharm and the plugin I really enjoy using them
Pingback: PyCharm: New PyCharm 2.0 EAP build: Jinja2,... | Python | Syngu
Good day, try to run new version and catch error (
sh pycharm.sh
Java HotSpot(TM) 64-Bit Server VM (build 20.2-b06, mixed mode)
Error occurred during initialization of VM
Could not find agent library yjpagent on the library path, with error: libyjpagent.so: wrong ELF class: ELFCLASS32 (Possible cause: architecture word width mismatch)
Ubuntu 11.04, extract archive to new folder.
I get the same error on my 64-bit Ubuntu. The workaround seems to be to add “64″ after the yjpagent to the last line in pycharm-108.1348/bin/pycharm.vmoptions:
-agentlib:yjpagent64=…
Thnx a lot, this help.
I become a Jetbrains client past year, buying the Personal License for PyCharm 1.0, but my license will expire next month in October, 28.
I’ve to buy a new license for the version 2.0, if the final release occur after the expiration of my license or I’ll be called to renew my license? Sorry, but I really don’t know how is the process to continue to getting support for PyCharm.
Thanks in advance.
If the final release happens after the expiration of your license, you’ll need to renew your license in order to be able to use PyCharm 2.0. The renewal costs about 60% of the full license price.
Cython!!!
Hmmm… what’s the second one? Cubstance? …
How to enable jinja2 support? I can’t see it in file types.
Settings | Template Languages
I can’t get the debugger to work for Pyramid projects.
C:\Users\swirsky\Documents\Projects\thrillscience\dayenu\env\Scripts\python.exe "C:\Program Files (x86)\JetBrains\PyCharm 2.0.1\helpers\pydev\pydevd.py" --multiproc --client 127.0.0.1 --port 2708 --file C:/Users/swirsky/Documents/Projects/thrillscience/dayenu/env/Scripts/pserve-script.py development.ini
pydev debugger: process 1156 is connecting
Connected to pydev debugger (build 111.107)
Starting server in PID 1156.
Unhandled exception in thread started by
Unhandled exception in thread started by
Unhandled exception in thread started by
Unhandled exception in thread started by
Traceback (most recent call last):
Traceback (most recent call last):
File "C:\Program Files (x86)\JetBrains\PyCharm 2.0.1\helpers\pydev\pydevd.py", line 170, in __call__
File "C:\Program Files (x86)\JetBrains\PyCharm 2.0.1\helpers\pydev\pydevd.py", line 170, in __call__
Traceback (most recent call last):
self.original_func(*self.args, **self.kwargs)
TypeError: ThreadedTaskDispatcher object argument after ** must be a mapping, not tuple
File "C:\Program Files (x86)\JetBrains\PyCharm 2.0.1\helpers\pydev\pydevd.py", line 170, in __call__
Traceback (most recent call last):
self.original_func(*self.args, **self.kwargs)
File "C:\Program Files (x86)\JetBrains\PyCharm 2.0.1\helpers\pydev\pydevd.py", line 170, in __call__
TypeErrorself.original_func(*self.args, **self.kwargs)
: TypeErrorself.original_func(*self.args, **self.kwargs)
ThreadedTaskDispatcher object argument after ** must be a mapping, not tuple: TypeError
ThreadedTaskDispatcher object argument after ** must be a mapping, not tuple:
ThreadedTaskDispatcher object argument after ** must be a mapping, not tuple
serving on http://0.0.0.0:6543
Robert,
Debugging Pyramid projects should work in PyCharm 2.0.2.