Re: deploying on apache as 'raw cgi' due to checkmate from mod_python etc

2010-01-20 Thread gs_toronto
Yup, it works using adapter as above and pysqlite-2.5.6. So I should be fine (until I run into some other reason why py2.3 isn't going to work for me). On Jan 20, 10:42 pm, gs_toronto wrote: > Thanks, I'll take a look at those. It also looks I was wrong about > 'pysqlite2' not being a replacement

Re: deploying on apache as 'raw cgi' due to checkmate from mod_python etc

2010-01-20 Thread gs_toronto
Thanks, I'll take a look at those. It also looks I was wrong about 'pysqlite2' not being a replacement for 'sqlite3' in Py2.5 - it looks like they are the same but pysqlite2 is arranged a bit differently, so the same import doesn't work; but it seems an adapter can be made so that 'import sqlite3'

Re: deploying on apache as 'raw cgi' due to checkmate from mod_python etc

2010-01-20 Thread Chris Lee-Messer
Yes, it is possible to serve django via cgi see http://code.djangoproject.com/wiki/ServerArrangements However, I would think that you would be better off one of several alternatives that use a second server to run django persistently. As one example, If you can use mod_rewrite on apache, you co

deploying on apache as 'raw cgi' due to checkmate from mod_python etc

2010-01-20 Thread gs_toronto
I have this apache installation which has mod_python, but that's bound to an existing python2.3 installation (which is in use for other web app, that uses compiled python extensions which won't work with py2.5). python2.3 doesn't have sqlite3 module (and 'pysqlite2' add-on isn't the same). So, I c