Comments on: Problems resolved http://thinkhole.org/wp/2005/11/30/problems-resolved/ www.thinkhole.org Tue, 02 Feb 2010 16:30:08 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: John http://thinkhole.org/wp/2005/11/30/problems-resolved/comment-page-1/#comment-20 John Thu, 01 Dec 2005 05:35:48 +0000 http://thinkhole.org/wp/?p=18#comment-20 Good advice indeed. I originally started out using the development server, but then I wanted to see if I could get it working with Apache2/mod_python. That went so smoothly that I forgot to switch back to the development server! Thanks again. Good advice indeed.

I originally started out using the development server, but then I wanted to see if I could get it working with Apache2/mod_python. That went so smoothly that I forgot to switch back to the development server!

Thanks again.

]]> By: Adrian Holovaty http://thinkhole.org/wp/2005/11/30/problems-resolved/comment-page-1/#comment-19 Adrian Holovaty Thu, 01 Dec 2005 04:04:56 +0000 http://thinkhole.org/wp/?p=18#comment-19 Ah, yes, mod_python caching is always something to keep in mind. It bit me several times back when I was learning it. In the grand scale of things, though, mod_python caching is a good thing -- it's why mod_python apps have such good performance. I'd definitely recommend using the "django-admin.py runserver" (development server) for Django development, in any case. Ah, yes, mod_python caching is always something to keep in mind. It bit me several times back when I was learning it. In the grand scale of things, though, mod_python caching is a good thing — it’s why mod_python apps have such good performance. I’d definitely recommend using the “django-admin.py runserver” (development server) for Django development, in any case.

]]>