Even through we didn’t discover any major regressions in PyCharm 2.6.3 Release Candidate, the feedback that we kept receiving from users led us to make a number of additional fixes, some of which are significant enough to warrant the release of another RC build. The specific areas affected by the fixes are diagrams, test runner (including support for the latest release of py.test) and remote interpreters.
Today we’ve published the Release Candidate build for the next bugfix update of PyCharm, version 2.6.3. Most of the improvements in this build are related to the underlying IntelliJ Platform (in particular CSS and LESS/SASS support got a number of nice fixes), but there’s a number of Python-specific fixes too, including a nasty deadlock during indexing, a fix for a long standing issue with coverage data not being displayed in the editor for some project configurations, and an NPE with remote interpreters.
As usual, the build is available for download from the EAP page. Please report any issues encountered to YouTrack. Provided that nothing major comes up, we’ll release the final 2.6.3 build this week, and proceed to open the EAP for PyCharm 2.7 after that.
The promised PyCharm 2.6.2 update is available. It contains critical fixes related to symlink handling, remote interpreters and copy/paste functionality in the editor. Some problems are fixed in code insight and the Django support. There’s also one small but nice addition — you can now use Zen coding in your Jinja2 files.
We’re currently composing the list of features for the next PyCharm version and all good pythonistas should easily guess which version usually follows 2.5 and 2.6
Stay tuned for further updates!
Today we’ve published the RC build for the next bugfix update of PyCharm. This build fixes critical issues related to symlink handling, remote interpreters and copy/paste, as well as problems with code insight and the Django support.
You can check out the complete release notes and download the new build from the EAP page. The update from the IDE will also become available in a short while, for those of you who have previously used EAP builds of PyCharm or set the update channel to EAP in Settings | Updates.
Provided that no new major problems turn up, the final 2.6.2 update will be out in a couple of days. And if you do run into problems, please report them to YouTrack.
PyCharm has been updated to support the new language features of Python 3.3:
yield fromexpression for generator delegation
u'unicode'syntax is accepted again for
raise ... from Nonesyntax for suppressing exception context
- Reworked I/O exception hierarchy
venvstandard library module (Python virtual environments, as in the popular
- Native support for implicit namespace packages
We’ve recorded a screencast What’s New in Python 3.3 as a quick introduction to the new features:
The source code used in this screencast is hosted on GitHub.
Back to School Sale!
Get up to 50% OFF personal licenses for PyCharm and other JetBrains products before September 14th.
Special offer details.
While being even more distributed than usually with part of the team at DjangoCon we’ve managed to complete the tasks we planned for PyCharm 2.6.
This update brings some big new features and many important improvements to the IDE:
- Class diagrams for any Python project, model relationships diagrams for Django, Google App Engine projects and SQLAlchemy ORM.
- Development of Web applications using the Flask microframework.
- Python 3.3 support.
- Many improvements in code analysis routines for Python and Django.
- Other additions for more productive coding.
PyCharm 2.6 is a free update for everyone who purchased their license after Sep 4th, 2011.
With the summer gone, it is just the time to run our yearly Back To School sale! And if you are not a proud owner of PyCharm license yet, you have a chance to save 40% off a personal license for the best Python and Django IDE.
- IntelliJ IDEA
- ReSharper (VB, C# and Full editions)
- dotTrace Performance
Think fast! It’s a limited-time offer that you don’t want to miss!
Your JetBrains Team
We’ve received a fair amount of feedback for our beta release (thanks everyone who reported issues!), and we’d like to give our users one final chance to try out a preview build and make sure there are no major problems remaining.
Today we’ve published the Release Candidate build of PyCharm 2.6. The changes worth noticing are fixes for performance issues caused by the Flask plugin, as well as some finishing touches to our Python 3.3 support. You can also check the complete release notes for the RC build.
See you next week at the DjangoCon US in Washington, DC!
We’re probably done with new features for this release and have just published a new build which we call PyCharm 2.6 Beta.
The major additions since the last EAP are the following:
- Diagrams support for SQLAlchemy
- Infer function return types from NumPy docstrings
- pyvenv & namespace packages support for Python 3.3
Check out the complete changelist for this build (121.141).
The Beta is available for download from a special page with all PyCharm 2.6 features overview.
There’s still time to do some polishing before 2.6 goes public next week and we really looking forward to your feedback on the Beta.
Next week is also a DjangoCon US. If you’re going, meet us there! We’ve also prepared some cool gifts for the attendees.
As you know, we’re a company of software products. PyCharm is one of 14 that are already known to the wider audience, and more are to come sooner or later.
But a company isn’t just what we develop. It’s also who we are, what we’re passionate about, what inspires us, and what we believe in. We decided to share these essential parts of our world called JetBrains with you — in the JetBrains Company Blog. In fact, it’s been in the works for quite some time and is finally coming to life.
Check in often to get to know us better — the people, the events, the hobbies, the beliefs, the anecdotes, special offers and the pure facts — everything behind the tools that we make for you.
Don’t miss our Interview with John Lindquist, already published on the blog.
Stay tuned for more news and keep developing with pleasure!
– Your PyCharm Team
Good news for everyone who uses gevent!
Since the last PyCharm 2.6 EAP our visual debugger is able to deal with gevent monkey-patched code.
To enable it just edit python/helpers/pydev/pydevd_constants.py in PyCharm installation and set the constant SUPPORT_GEVENT=True
Your feedback is welcome as always!