Hi,
Don't forget "yolk". Very powerful tool to display virtualenv contents
in readable format. You can install it with pip install yolk.
15.10.2012 9:00, Frank Bieniek kirjoitti:
Hi,
do a "pip freeze" after you have activated your environment,
this way you see the packages that are visible
Hi,
do a "pip freeze" after you have activated your environment,
this way you see the packages that are visible to the python interpreter
inside your virtual env.
Possible Problem
You have installed all packaged before you created the virtual env.
-> virtual env shows no components.
pip
Sweet! Thank you!
On Monday, October 15, 2012 12:56:37 AM UTC-4, Jani Tiainen wrote:
>
> Because the setup procedure used there is faulty.
>
> This is what happens:
>
> When installing Python install package will bind .PY(C) file execution
> to use _always_ main installation. It won't follow
Because the setup procedure used there is faulty.
This is what happens:
When installing Python install package will bind .PY(C) file execution
to use _always_ main installation. It won't follow any path settings
which virtualenv relies on.
I'm not sure can you even overcome that restriction
I suppose I was a little light on the details of how I setup the
environment. I don't often setup a new environment from scratch so I used
this post as the basis:
http://slacy.com/blog/2011/06/django-postgresql-virtualenv-development-setup-for-windows-7/
The versions of each program I used /
This is probably a VirturalEnv problem as opposed to a Django problem but I
was wondering if someone here could point me in the right direction.
I'm trying to setup clean environment for a demonstration of Django on
Tuesday but I get the following when I try to setup the project within the
6 matches
Mail list logo