On Thu, Oct 8, 2009 at 4:23 PM, Christopher Arndt <[email protected]>wrote:
> > Dan schrieb: > > Now the same thing from within the virtualenv: > > > > ImportError: No module named Bio > > > > I tried loading the Bio package using 'easy_install biopython,' which > > looks like it worked just fine, but python still has no luck finding > > the Bio package within the virtual environment. > > > > Must be another step I'm missing somewhere. Any ideas? > > Did you activate the virtual environment? > > source /path/to/env/bin/activate > > You have to do this before you install anything in the virtual > environment with easy_install. > > If you just want to use the virtual env for running python, it is enough > to run the python executable from the "bin" directory of the virtual > env, e.g. /path/to/env/bin/python <yourscript>, but it's usually easier > to just do the "source" comamdn given above before you begin your work. > > See http://pypi.python.org/pypi/virtualenv for details. > > Chris > > Turns out what was killing access to the Bio package was the "--no-site-packages" parameter that was added to the virtualenv command per the install directions. Once I omitted this parameter I was able to get the job done. This may not isolate the environment as well, but it works and I'm proceeding with the project. Thanks for your help. Dan --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
