I'm attending OSCON, and will be in the Django Tutorial on Monday as
will a few other people from my division at O'Reilly. I'd be rather
interested in talking frameworks and WSGI or perhaps having a little
Python web developer meet-up.
Lookin forward to a release with the magic-removal stuff.
Ch
I'm inclined to agree with Ian on this. I've had very bad experiences
with the Rails version of schema migrations, and having to restore db
backups, then try them over and over when screw-ups happen (which ALTER
statements always seem to cause when attempted in a cross-db way).
Despite how many p
Yes, sort of. TurboGears is using what they're calling the "open
template plug-in engine" something or rather. The underlying effect is
it provides a unified way to render templates. It's still undergoing
some fine-tuning, and is not part of TurboGears itself. Here's the
'spec' for making a templa
Adrian Holovaty wrote:
> Anybody care to tackle the separation of Django templates? The main
> thing is decoupling it from django.core.settings (and, hence,
> DJANGO_SETTINGS_MODULE), of which I'm not sure what the best approach
> would be. Note that in the magic-removal branch, the template syste
