Friday, December 10, 2010

Improved unittest support in Pydev

Pydev 1.6.4 is still not released, but the first nightly with the new support for unittest is now available (see http://pydev.org/download.html on instructions for getting the nightly).

The major features added are:

1. A PyUnit view is now available to show the results of unittests
2. The nose and Py.test test runners are now also supported





The interesting features related to seeing the tests are:

- The results of tests are shown, along with a green/red bar (or if you're with Aptana Studio, following the color theme)
- The time a test took to run is shown (and may be used to sort the tree)
- The errors/output are shown by selecting the test run or just hovering over the items
- A filter to show only errors is available

And there are some interesting actions in that view too:

- A test session can be rerun
- A new test session can be created to rerun only the errors of the current run
- The test session can be stopped
- The results of a previously run test session can be seen again

And at last (but not least), the test runner can now be configured, so, one can use the test runner bundled in Pydev, Nose or Py.Test.

The preferences page to configure it can be accessed in the 'Configure test runner preferences' in the PyUnit view.





Enjoy!

Sunday, November 21, 2010

What's next in pydev?

Ok, this release is taking more time than usual. What happened is that the main target of the release changed after I started working on it (due to popular demand).

So, the next 2 releases will be targeted at those that use unit-tests a lot -- such as myself :)

I won't put on more details right now, but as soon as things are ready for testing (probably at mid-end December) I'll post again about it.

In the meanwhile, critical bugfixes are being fixed and nightly builds are being issued with those fixes if anyone needs those. So, the current nightly is actually the last stable version + bugfixes -- new things are in a branch called 'nose' -- which should give a hint on what's being worked on from its name :)

Tuesday, October 05, 2010

Pydev 1.6.3 released

Yes, Pydev 1.6.3 is out.

This is mostly a bug fix release, but there are still some noteworthy things, such as new icons, a better editor preferences explaining how to properly configure the themes when using Aptana themes and an improved code-completion for keywords.

See the full details at http://pydev.org/

Enjoy!

Tuesday, September 07, 2010

Pydev 1.6.2 released

The latest Pydev version is out.

The Django Templates Editor is the major thing in this release, supporting html files with html, css and javascript.

The current Pydev is now also integrated in Aptana Studio 3, so, a full download where Pydev (with the Django templates editor) is already pre-installed is available at: http://aptana.com/products/studio3/download.

Also noteworthy is that the Python 2.7 grammar is fully supported (and a bunch of bug fixes have been made available).

Thursday, August 19, 2010

Django Templates Editor

Note: The new recommended way of having a Django Templates Editor is by using LiClipse: http://brainwy.github.io/liclipse/ (which is a commercial counterpart made to keep PyDev supported, as such it has PyDev standalone and a bunch of other goodies builtin).

Aptana Studio 3 still has PyDev and its own Django Templates Editor, but the bundled PyDev version is not kept up to date.

Below are more details on the integration on Aptana Studio 3 (using the Aptana Themes)






The highlighted tokens are the ones defined in the templates in the "Django tags" context (so, tags to be highlighted can be added or removed).





Also, there's code completion based on templates for the django-templates related stuff and pretty nice html completions inherited from the Aptana html editor.

The image below shows the html completions, a django-templates template completion and its result and a django-templates template completion for the filters.




That's it for now. Please grab it and let me know if it's working or if there's a bug lying around there so that it can be fixed before the official release :)