@@ -77,7 +77,12 @@ The issue has been reported on the virtualenv bug tracker `here
77
77
<https://github.com/pypa/virtualenv/issues/54> `__ and `here
78
78
<https://github.com/pypa/virtualenv/issues/609> `__
79
79
80
- Until this is fixed, a workaround is needed. The best known workaround,
80
+ Until this is fixed, one of the following workarounds must be used:
81
+
82
+ ``PYTHONHOME `` Script
83
+ ---------------------
84
+
85
+ The best known workaround,
81
86
borrowed from the `WX wiki
82
87
<http://wiki.wxpython.org/wxPythonVirtualenvOnMac> `_, is to use the non
83
88
virtualenv python along with the PYTHONHOME environment variable. This can be
@@ -108,6 +113,27 @@ framework build within the virtualenv. To run a script you can do
108
113
framework build. To run an interactive ``IPython `` session with the framework
109
114
build within the virtual environment you can do ``frameworkpython -m IPython ``
110
115
116
+ ``PYTHONHOME `` Function
117
+ -----------------------
118
+
119
+ Alternatively you can define a function in your ``.bashrc `` using
120
+
121
+ .. code :: bash
122
+
123
+ function frameworkpython {
124
+ if [[ ! -z " $VIRTUAL_ENV " ]]; then
125
+ PYTHONHOME=$VIRTUAL_ENV /usr/local/bin/python " $@ "
126
+ else
127
+ /usr/local/bin/python " $@ "
128
+ fi
129
+ }
130
+
131
+ This function can then be used in all of your virtualenvs without having to
132
+ fix every single one of them.
133
+
134
+ PythonW Compiler
135
+ ----------------
136
+
111
137
In addition
112
138
`virtualenv-pythonw-osx <https://github.com/gldnspud/virtualenv-pythonw-osx >`_
113
139
provides an alternative workaround which may be used to solve the issue.
0 commit comments