setting PYTHON_EGG_CACHE doesn't do anything
- From: Brett Neumeier <random (at) rnd.cx>
- Date: Sun, 19 Feb 2006 12:20:22 -0600
On Sun, 2006-02-19 at 00:01 -0700, Jeremy Herbison wrote:
> I get the following error using mod_python and SQLite (latest stable
> versions of everything:
When you say "latest versions of everything", what version of pysqlite
does that mean? I tried getting trac working with pysqlite 2.1.3,
failed, and went back to 2.0.7.
> The recommended solution, setting:
>
> SetEnv PYTHON_EGG_CACHE /tmp
>
> in httpd.conf fixes the problem if I use CGI, but I'd rather use mod_python
> for obvious reasons. It doesn't seem like adding the SetEnv does anything at
> all since the error log always says "/root/.pything.eggs".
Here's what I did. I reasoned that the egg file is unpacked so that
some of its files are available as real files in the file system, and I
wasn't getting any bonus points for having the egg present in python's
site-packages directory as a file anyway. So:
cd /path/to/python/site-packages
mv pysqlite-2.0.7-py2.4-linux-i686.egg foo.zip
mkdir pysqlite-2.0.7-py2.4-linux-i686.egg
cd pysqlite-2.0.7-py2.4-linux-i686.egg
unzip ../foo.zip
rm ../foo.zip
Now the egg file is unpacked, so the files are all present already in
the filesystem, nothing needs to be unpacked, PYTHON_EGG_CACHE is
irrelevant, and everybody is happy.
Perhaps that would work for you as well?
--
Brett Neumeier <random (at) rnd.cx>
_______________________________________________
Trac mailing list
Trac (at) lists.edgewall.com
http://lists.edgewall.com/mailman/listinfo/trac