Ahh, right, I ran into that too under mod_python.  Trac does have a 
habit of overriding python error messages in some places.

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.
>
> I figured it out by a python cgi test script which tryed just to
> import psycopg2, and then there was the correct error message.
>
>
>
> On 28. Jan 2009, at 16:53 Uhr, Shane Caraveo wrote:
>
>
> On 1/28/09 7:35 AM, Karsten Fuhrmann wrote:
>> Hello,
>
>>     File "/usr/lib/python2.4/site-packages/Trac-0.11stable_r7802-
>> py2.4.egg/trac/db/postgres_backend.py", line 118, in __init__
>>       from pyPgSQL import PgSQL
>> ImportError: No module named pyPgSQL
>> Any Directions?
>
> Python is not finding the psycopg module on PYTHON_PATH, at least that
> is what I recall when I ran in to that a while back.  Since you're using
> fastcgi, there is probably some mechanism to specify that in the
> apache/fastcgi configuration.  I had to do something similar with wsgi
> and mod_python.
>
> Regards.
> Shane
>
>
>
>
>
>
> Greetings,
> Karsten Fuhrmann
> System Administrator
> Cartoon-Film Thilo Rothkirch
> Hasenheide. 54
> D-10967 Berlin
> phone  +49 30 698084-109
> fax  +49 30 698084-29
> mobile  +49 172 3859543
>
>
>
>
>
> >


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to