Manipulation of PYTHONHOME destroys ability to deactivate
I need to manipulate PYTHONHOME from postactivate script. (Reason: wxpython needs a framework install of python to provide access to the MAC OSX GUI - see: http://wiki.wxpython.org/wxPythonVirtualenvOnMac for more details).
I then restore PYTHONHOME from predeactivate script. When I deactivate - the script cannot run because even though it is using the python interpreter at VIRTUALENVWRAPPER_PYTHON the setting of the PYTHONHOME does not allow it to find the base virtualenvwrapper module.
Should the various "python -c" calls also include "-E" so PYTHONHOME is ignored? (although I believe PYTHONPATH is ignored too which may not be the solution)
Is there another way to easily keep a virtualenv but utilize a framework install binary such that MAC OSX GUI will be able to be accessed by wxpython?