I think the tricky part is what Guillermo is saying. All views take a request object and return a response object. You'd have something that would have to mimic HTTP requests and work with HTTP responses. At that point it seems like you should just create your MVC pattern-based app using an ORM (sqlalchemy?) and tie it to whatever front-end your going for. (Just giving examples of what might be attractive in Django to have in a non-web app.)
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
