debugger

As some of you might know, until last week Reddit was open source. But we can still go to GitHub and check out a version of the source. So let’s go ahead and play around with it! Things you’ll need to follow along Reddit uses Vagrant to spin up a pre-configured development VM on demand. To be able to use it you’ll need: Vagrant VirtualBox Connecting to virtual machines for debugging is a feature that is only available in PyCharm Professional Edition. If you haven’t got it yet, you can get a free trial from our website. Check out Reddit To start, we need to get the code, so let’s

We're happy to announce the beginning of the Early Access Preview program for PyCharm 2.7. The new version is focused on improving our support for core Python development and is planned for release before the end of this year. As usual, EAP builds are not feature complete and are likely to contain bugs, but they give you a chance to provide feedback on the new features and ensure that the final production release meets your requirements. New and noteworthy in this release: PyCharm's debugger is now capable of collecting type information at runtime and makes use of this information for impr

This week's EAP build of PyCharm 2.0 is probably going to be the last one before the Beta release, and as such, it brings the last major batch of new features to be included in PyCharm 2.0: When opening a project, you now have an option to add it to the projects already open in the current window; The JavaScript debugger is now included in the PyCharm distribution and integrated with the Django server run configuration; The Python and Django consoles now support customization, including the possibility to specify a script which is automatically executed when the console is opened; You ca

During the past two weeks, the PyCharm team has mostly been focused on bringing the features we've already started (such as Mako and Cython support) closer to release condition, rather than delivering splashy new stuff. However, there are some new features that I would like to specifically highlight: Navigation from the text inside of a {% trans %} or {% blocktrans %} tag in a Django template to the .po file; Intention to wrap a block of text inside a Django template in a {% trans %} or {% blocktrans %} tag (immediately extracting the text to the .po file); Possibility to debug an applicati

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 met

While more new features are introduced to PyCharm 2.0, the older ones are also being developed — namely Django template debugger, which first appeared in version 1.5. Now I would like to promote it one more time in order to ask for some feedback for a future development or just inform those who didn't know about it yet. How to use the template debugger? Very simple! Just place a breakpoint in your template file at a line with any Django tag or expression. Run Django server in Debug mode (Shift+F9) and make it render the template (e.g. open the page in your browser). Voilà! The se

PyCharm 1.5 final release is now available for download. It's been an interesting version to work on. We've added a number of useful features that should make you more productive and your code better. Here are the main new features you will find inside PyCharm 1.5: Ultimate support for documentation (external documentation, Epydoc and reStructuredText markup, docstring stub generation etc.) Django Templates Debugging Database support in Django applications (autodetection, .sql files editing aids, database tables browsing, etc.) New 'Move Class/Function' Refactoring Many IDE improvement

Today we're happy to announce the immediate availability of the first Early Access Preview build of PyCharm 1.5, the next major release of PyCharm. The big theme of this release is a comprehensive documentation support. PyCharm now understands not only your code, but also the documentation surrounding it. The big theme boils down into a number of specific features described below: External Documentation Rendered Docstrings Syntax Highlighting and Completion in Docstrings Docstring Stub Generation reStructuredText support Another big addition in this release is Django templates debugging

Recent PyCharm 1.1 EAP has added one of the most voted feature — Remote Debug. I'm going to say a few words about it expecting you to try it and share your thoughts with us. If you plan to debug something "remote" it means that you have: a project that you develop locally in PyCharm the same project at some remote host (note that sources really should be the same, otherwise you will see some strange things happening during debug session, e.g. inability to set breakpoints or seeing current execution point different from actual one) local host accessible from the remote one by socket con

Now that the stress of the IntelliJ IDEA 10 release is behind us, we can return to the regular schedule of PyCharm 1.1 Early Access Preview builds. During the three weeks that have passed since the previous EAP, the PyCharm team has created quite a few new features: Initial support for remote debugging, the most highly voted feature in our issue tracker; New test runner for nose tests, with support for nose plugins; Several new quickfixes, for example, one to add forgotten 'self.' qualifier for instance attribute access; New intentions, such as 'join ifs'; Support for Python 3 parameter and fu