On Wednesday 22 July 2009 04:59:14 killer chicken wrote: > Did yqu by any chance use the --no-site-packages-option when creating > the virtualenv? > > yes I did, what is the matter with that?
As documented in the virtualenv-docs, it prevents a venv from accessing the system's python (or base installation) site-packages. Which is sometimes a good thing, but not if you can only get certain packages to install there. > > > (tgenv)$ python > > > > > > >>> import sys > > > >>> sys.path > > > > > > gives you? Does it include the path where matplotlib is installed? > > ['', > 'C:\\Python25\\lib\\site-packages\\setuptools-0.6c9-py2.5.egg', > 'C:\\Pythonlib\\site-packages\\docutils-0.5-py2.5.egg', <snip/> That doesn't look good, because you seemingly didn't activate the venv before installing TG2. I suggest you clean out the site-packages from everything TG2 has installed. > > It doesn't include matplotlib, althouh matplotlib is in C:\\Python25\ > \lib\\site-packages\\ indeed This is strange, but somehow your installation seems to be botched. > > > I have Linux debian (but I don't probe the app there :( ) also I > > have windows XP > > I will try with pydev and add source to pythonpath (I don't know how > to do it throw a console) and see what happens I don't use pydev, and I don't see how that helps here. However, you can add a virtualenv-python-interpreter to pydev, then you get all it's sys.path-entries. Diez --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
