Have just finished reading through the tutorial. Unfortunately, after finding the solution to the admin interface not showing up (you have to specify the "admin" settings file, despite the tutorial's assertion that the two settings files are the same), ran into a failure with a many-to-many relationship (can't delete). No big deal, still able to read the tutorial.
Haven't yet seen anything that explains how to deploy the application (i.e. not running it with the "don't use this in a real-world situation" devel servers), but I can't imagine it's too involved.
The approach is close enough to my own web framework for BasicProperties that I'd imagine I can adapt to it fairly easily. Still that means I'll have two web frameworks to keep up with (Nevow and Django), but that's markedly better than raw CGI
.I guess the next step is to build a real-world application with it. I'm thinking the first candidate would be py3d.py (my collection of links to Python 3D projects, currently coded as a straight CGI and edited directly to produce new items).
One thing I'm missing from Nevow is the LivePage technology
. I rather enjoyed playing with that. I wonder how hard it would be to make Django Twisted-compatible (i.e. non-blocking)... or maybe it would be easier to add the XMLRPC mechanisms to Django. Also wondering how complex it would be to make the models, validators, URL handlers etceteras work within Zope.Which brings us back to the "we really need to unify the web frameworks" topic...
two things to note:
http://www.djangoproject.com/documentation/tutorial2/
clearly tells you to use myproject.settings.admin for the admin site.
http://www.djangoproject.com/documentation/modpython/
tells you how to setup mod_python...
Django-on-Twisted:
http://code.djangoproject.com/ticket/172
This might become something like LivePage:
http://opensvn.csie.org/django_ajax/trunk/
Justin: yes, the page does tell you to use admin, but every point up to then has been suggesting that you just set the environmental variable and forget about passing in the parameter. It's not a bug, just something that could use a note.
Thanks for the pointer to the mod_python setup.
JanC, thanks for the pointer, will look at it when I get back to playing with Django.
You know, I logged this a long time ago in a ticket and it was just blown off.
Many others have had this problem too from the IRC logs. It should really be clarified.
http://code.djangoproject.com/ticket/79
soap/xmlrpc with django are easy!