Revision history [back]
In general the way to activate a virtualenv for a debug or test process, or for the Python Shell, is to set the Python Executable to Activated Env and specify the full path to the activation script. This can either be in Project Properties under the Environment tab or in a Launch Configuration created from the Project menu.
If your tests use a different env than your project in general, you would need to create a launch configuration and either use it in the Environment in the Testing tab of Project Properties (for all tests) or in the File Properties on a specific test file (if just one test file is using that env).
Some relevant docs:
- https://wingware.com/hints/environments
- https://wingware.com/doc/howtos/virtualenv
- https://wingware.com/doc/proj/launch-configs
Please don't hesitate to ask if this isn't clear.
In general the way to activate a virtualenv for a debug or test process, or for the Python Shell, is to set the Python Executable to Activated Env and specify the full path to the activation script. This can either be in Project Properties under the Environment tab or in a Launch Configuration created from the Project menu.
If your tests use a different env than your project in general, you would need to create a launch configuration and either use it in the Environment in the Testing tab of Project Properties (for all tests) or in the File Properties on a specific test file (if just one test file is using that env).
Some relevant docs:
- https://wingware.com/hints/environments
- https://wingware.com/doc/howtos/virtualenv
https://wingware.com/hints/environments https://wingware.com/doc/howtos/virtualenv
https://wingware.com/doc/proj/launch-configsPlease don't hesitate to ask if this isn't clear.