External console error (mac)

edit

Thanks for your quick reply. I will try your suggestion and will be looking forward to the update.

Just a follow-up. By using your suggestion I was able to get this to work. I also had to add an environment variable (TERM=xterm-256color) in the Environment settings box via "Add to inherited environment" option. This entry was needed because of my use of the python "curses" library.

Thanks. I looked at this in a bit more detail and the issue we load the env after the virtualenv launcher helper is run. I'm not sure how hard this will be to fix, but using Command Line instead is functionally identical for virtualenvs.

Not relevant to you but maybe useful for others: I think using Command Line won't work for conda envs without further manual setup of the environment. This problem is mentioned under About Anaconda Environments in https://wingware.com/doc/howtos/anaconda and a possible work-around for that case would be to activate the conda env on the command line and that start Wing from that env. Or the PATH can be modified to add Anaconda's library directories so the DLLs can be loaded (that could be done in Environment in Project Properties so Wing doesn't have to be launched in the activated env).

This is still an issue right now. Any sight on a fix?

Did you try setting the Python Executable to Command Line and entering the full path to the virtualenv's 'python' instead? That's functionally identical to using Activated Env with the full path to the 'activate' script, and it should work around the problem. The only possible exception to that might be some versions of Anaconda, as noted above.