> On 1/28/09 8:03 AM, Karsten Fuhrmann wrote: >> Thanks, for the info. I just solved it myself. >> The ImportError is quite incorrect because the problem was that it >> could not extract the egg. There was a permission problem. >> I just changed the PYTHON_EGG_CACHE Environment Variable to a >> directory writeable by the webserver, and it worked.
Shane Caraveo wrote: > Ahh, right, I ran into that too under mod_python. Trac does have a > habit of overriding python error messages in some places. So, the real problem here is that there is a fallback mechanism in trac wrt PostgreSQL support. First it looks for psycopg. If it can't find it (ie, can't import it), then it tries to import pyPgSQL. That's why you end up with the error message about pyPgSQL. It may be worth noting in the log that psycopg2 failed, as that's probably the largest (and indeed recommended) installation base. -John --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
