Ask Your Question

Revision history [back]

I'm glad you got it working, although I also don't understand what was going on. Opening a new window with New Tool Window doesn't open the window in any different environment. If you activate a virtualenv from the command line and start Wing also from that command line then it does inherit the env. You can also set Python Executable in Project Properties, from the Project menu, to the full path of the virtualenv's Python, which is the value of sys.executable (after 'import sys') in the virtualenv. Then it uses the right virtualenv for that project without polluting the environment if you switch to other projects (in that model, you would start Wing from the Start menu and not the command line, or at least not from a command line where you've activate a virtualenv). There are some details on using Wing with virtualenv here: http://wingware.com/doc/howtos/virtualenv

I'm glad you got it working, although I also don't understand what was going on. Opening a new window with New Tool Window doesn't open the window in any different environment.

If you activate a virtualenv from the command line and start Wing also from that command line then it does inherit the env.

You can also set Python Executable in Project Properties, from the Project menu, to the full path of the virtualenv's Python, which is the value of sys.executable (after 'import sys') in the virtualenv. Then it uses the right virtualenv for that project without polluting the environment if you switch to other projects (in that model, you would start Wing from the Start menu and not the command line, or at least not from a command line where you've activate a virtualenv).

There are some details on using Wing with virtualenv here: http://wingware.com/doc/howtos/virtualenv