Revision history  [back]

One idea is set your Python Executable in Project Properties (or in a launch configuration if that is what you are using) to Activated Env and specify the full path to your environ.bat. That does run the .bat in a way that causes your debug process to inherit the env.

If you're using a virtualenv, have your environ.bat setup .bat also call the virtualenv's activate.bat.

If you're not using a virtualenv and Wing doesn't run the right Python then you could prepend the 'bin' directory for the Python you want to use to the to PATH env in your activate.bat.

I suspect this will solve it... please let me know if not.