Just a quickie…
To make SciTE work with scss files (which are enhanced css files), just add the following information:
In /usr/share/scite/SciTEGlobal.properties (on a Fedora machine at least, YMMV) :

;*.scss to the end of source.files=

and in /usr/share/scite/css.properties the top of the file should read :

filter.css=CSS (css scss)|*.css;*.scss|
lexer.*.css=css
lexer.*.scss=css

After looking around the web for an SQLalchemy model migration assistant, we found no satisfactory equivalent to the migration tool that people love for Ruby.
In particular sqlalchemy-migrate seems like it’s an overkill (in addition, sqlalchemy-migrate is fiddly to set up with Pylons).
There’s also a project call miruku, but that is also a little illusive, somehow.
PLATFORMedia [...]

sass (and its successor scss) is a really nice CSS meta-language, enabling nicer hierarchies of classes to be built (much more maintainable).  The transformation software is written in ruby, and provided by the ruby gem haml.
The first step when using SCSS file, is usually to recast existing CSS files into semantically equivalent SCSS files (when [...]

Just a quickie…
To make SciTE work with mako files (which are template files used by the mako templating system included with Pylons), just add the following :
In /usr/share/scite/SciTEGlobal.properties (on a Fedora machine at least, YMMV) :

lexer.html.mako=1