Pythonpath and trac.scripts.admin

[anonymous]

I get the "ImportError: No module named trac.scripts.admin" error. I looked at the previous tickets, and someone else had this error, and the solution was to set the pythonpath variable. I am trying this but to no success.

I am running tcsh, and have installed track in my home area, ~ME/trac. I am running trac-admin in the ~ME/trac/bin area, and I've tried setting the PYTHONPATH using

set PYTHONPATH=(~ME/trac)

but I still can't past this issue. Your help would be appreciated. Thanks.

[Emmanuel Blot]

We really need a 'how to report a bug' page…

Please specify which version of Trac you're using.

[anonymous]

I am using trac-0.10.4.

[Emmanuel Blot]

Replying to anonymous:

I am using trac-0.10.4.

See the dedicated field Version in the ticket page. Thanks.

[anonymous]

Funny! Thanks.

I'll put in another ticket regarding the very hard to use drop downs with labels.

I'm just kidding, of course. Thanks for putting up with us idiots.

[hyuga <hyugaricdeau@…>]

Regardless, I'd say this is an installation issue…

[anonymous]

In case it helps others in their attempts to install:

I couldn't get things to work because of my default shell environment, i.e., because I am using tcsh, I could not get python (trac-admin) to recognize the PYTHONPATH.

So, if you installed trac locally because you did not have admin rights to install in /usr area, you need to set the PYTHONPATH to your trac site-packages location (EXPORT PYTHONPATH=/path/site-packages), and retry trac-admin from the bash shell prompt.

[lkraav <leho@…>]

ran into this in my 0.10 virtualenv today for testing ​TracForgePlugin. exporting pythonpath also worked here. why doesn't virtualenv do this automagically..?