Subject: Re: Re: pysqlite works, but not with mod_python - msg#00027

Previous Message by Date: click to view message preview

Re: pysqlite works, but not with mod_python

Yes, I have seen that too, but thought that I don't have to disable SELinux just to get pysqlite + mod_python working together. There is also some info on http://projects.edgewall.com/trac/wiki/TracWithSeLinux about SELinux + Trac, but since I'm not running Trac I thought this doesn't apply to me (but perhaps is still relevant for pysqlite). In any case if it is not possible to run pysqlite through mod_python + apache with SELinux enabled, then I would say this is a bug (but in which component?....). Or is it really unavoidable due to the internal working of SELinux? > > Google at http://lists.edgewall.com/archive/trac/2005-August/004252.html > suggests it's got to do with SELinux. >

Next Message by Date: click to view message preview

[ANN] pysqlite 2.1.2

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 pysqlite 2.1.1 fixed an obscure bug: it was possible to get crashes by executing the same DML statement twice, like this: from pysqlite2 import dbapi2 as sqlite con = sqlite.connect(":memory:") con.execute("create table foo(bar)") con.execute("create table foo(bar)") pysqlite 2.1.2 contains a better fix for the bug, which also makes sure that you always get an error message in cases like this. There were also a few changes to setup.py, which can now allow you to do things like $ python setup.py build_docs $ python setup.py test but they're not documented yet. Downloads of sources and Python 2.4 or Python 2.4 Windows binaries at http://pysqlite.org/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFD0Z9xdIO4ozGCH14RAlJEAJ9bCexvUxhrjHRa3bRonR1Fr1SH/wCdFQIf 8gzwkL+tqnt0n1FBv/EgWUI= =52cn -----END PGP SIGNATURE-----

Previous Message by Thread: click to view message preview

Re: pysqlite works, but not with mod_python

Yes, I have seen that too, but thought that I don't have to disable SELinux just to get pysqlite + mod_python working together. There is also some info on http://projects.edgewall.com/trac/wiki/TracWithSeLinux about SELinux + Trac, but since I'm not running Trac I thought this doesn't apply to me (but perhaps is still relevant for pysqlite). In any case if it is not possible to run pysqlite through mod_python + apache with SELinux enabled, then I would say this is a bug (but in which component?....). Or is it really unavoidable due to the internal working of SELinux? > > Google at http://lists.edgewall.com/archive/trac/2005-August/004252.html > suggests it's got to do with SELinux. >

Next Message by Thread: click to view message preview

Re: Re: pysqlite works, but not with mod_python

Hi, thanks for the reply, and indeed, it was a SELinux problem. It seems there is a way to have SELinux enabled and still run pysqlite through apache but it's too complicated so I just disabled SELinux and that solved the problem.  I'm 99 % sure it's an SELinux configuration problem. Maybe some .so file you installed has wrong permissions. Maybe you need to run a SELinuxcommandline utility so that it accepts the new binaries ...Maybe there's more detailed information to get out of SELinux other than"permission denied" by looking at server logs. I don't know - I've never used SELinux myself ...-- Gerhard _______________________________________________ Pysqlite mailing list Pysqlite-IAPFreCvJWPBWskQ1e/+sw@xxxxxxxxxxxxxxxx http://lists.initd.org/mailman/listinfo/pysqlite