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 :)

Pydev 1.6.1 released

This release was anticipated a bit because of a critical fix to the debugger, which was not working in python 3 (the thread module was renamed to _thread and this wasn't properly dealt with).

Also noteworthy in Pydev 1.6.1:

There are actions to restart the last launch (Ctrl+Shift+F9 in pydev editor) and terminate all launches (Ctrl+Alt+F9 in pydev editor). Buttons were also added in the console output view of pydev launches to activate those (so, it's now easier to restart a given launch after code-changes).

2to3 is now integrated in pydev. To use it right click a folder or file and choose the menu "Pydev > Apply 2 to 3".

Enjoy!

Code-completion in debugger (Pydev 1.6.0: testers needed)

Pydev 1.6.0 should be released on Tuesday (if no bugs are found until then).

The major work in this release was on the debugger, with:

1. code-completion in the console (as the image below shows)



2. Code entered is evaluated on a line-by-line basis (previously an empty line had to be entered before the evaluation)

3. There's a way to work with the stack of unhandled exceptions in the debugger. There's still no way to add it in the gui, so, one has to call pydevd.set_pm_excepthook() from within the program to handle those (the module will be there whenever running in debug mode). Note that if sys.excepthook is already changed within the program, this call has to be done after that change (it will call that function and show it in the pydev stack frame right after that)

Aside from that, pydev is now compatible with Aptana Studio from 2010-07-12 and there's a fix for one really annoying bug in the compare editor when applying a patch.

Preparing for Pydev 1.5.8 (testers needed)

Pydev 1.5.8 is now in polish mode for a new release, so, anyone wanting to test it, this is a good time (and it should be pretty stable already). Just grab the nightly to test it: See: http://pydev.org/download.html for instructions.

The major change is that Pydev now takes advantage of the newest features in Aptana 3 (beta).

Noteworthy features incorporated:

1. Theming: The colors in the chosen theming (Preferences > Aptana > Themes) are properly used.



2. Find Bar: Instead of the default Find/Replace dialog, a find bar is shown at the bottom of the editor for doing common searches (and the next Aptana release will also add replace actions to that bar).



Some other niceties include:

- An additional choice for the title of django editors, showing a different icon but still adding the regular name of the file to the title was added.

- Jars are now signed (some people were getting corrupt installs with problems when downloading pydev, so, this will hopefully fix that).



- A bunch of bug-fixes :)

Pydev 1.5.7 released

It's just out and it's an almost required update (a critical bug was fixed in the debugger which could make it skip breakpoints).

Aside from that, many other niceties were added:

- Performance for really large files got considerably better
- The interpreter configuration will only update what's needed (duh)
- Editors have a unique representation considering all editors currently open
- Etc. See: http://pydev.org/ for details.

Enjoy!