[Trac] setting PYTHON_EGG_CACHE doesn't do anything
subscribed at red56.co.uk
Sun Feb 19 16:20:11 CST 2006
when dealing with eggs and apache, it seems to be best to make sure they
are installed unzipped: the easiest way to do this is to supply a "-Z"
arg to easy_install when you setup... (I'm not at all a trac expert, but
I've experienced similar issues with turbogears) -- though I don't
really get why you have an egg installed at all, having looked at the
install instructions for pysqlite & for trac, it doesn't appear likely
that an egg would be installed (unless pysqlite is required as a
dependency by trac's install, but I don't think that's true...)
As to your environ q, I wonder whether, given that the egg may be
already unzipped by the time that modpython gets to it, it ignores the
PYTHON_EGG_CACHE variable and uses the default value instead?
I'd guess that the answer, in any case, won't be on the trac forum, but
you might try looking at the peak site (e.g.
who are, I believe the maintainers of the "egg" implementation.
Jeremy Herbison wrote:
>> 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>
> That does work, and thanks. I am sort of intellectually curious though as
> to why the python interpreter is not honouring the environment variable.
> Trac mailing list
> Trac at lists.edgewall.com
More information about the Trac