LoCo tools, development
Neal McBurnett
neal at bcn.boulder.co.us
Thu May 22 07:54:13 BST 2008
On Thu, May 22, 2008 at 12:16:52AM -0600, NICK VERBECK wrote:
> One of the projects I am heading up is a web framework for LoCo's
> powered on Django. It has been slow moving as I haven't had the time
> as of late to get the core up but a lot of ideas have been floating
> about and a few have been put into the Blueprints on Launchpad and the
> wiki.
>
> The only thing I've been contemplating is weather to keep with Django
> or move to Pylons or Turbogears 2. As both support the WSGI standard,
> and I have yet to hear anything from Django as to them moving to the
> standard. WSGI allows you to switch out any component of you base
> framework with another with out much work. i.e. If you don't like SQL
> Alchamy as your ORM then change it out with something else. This may
> be something I put up in front of the group to debate on.
>
> You can find the project here https://edge.launchpad.net/loco-django
Django has supported WSGI for a while:
http://www.djangoproject.com/documentation/faq/
and you can mix-and-match components. It integrates and documents
them nicely, so you may not want to, but it is flexible enough to do
it.
Neal McBurnett http://mcburnett.org/neal/
More information about the loco-contacts
mailing list