Yeah, that's an artifact of the days when folks would manually edit the
variables in this script to customize their install. You couldn't count on
WORKON_HOME being the same as PYTHON_HOME.

virtualenvwrapper uses WORKON_HOME when setting up the virtualenv in
mkvirtualenv. Perhaps it would be better to either add some documentation
explaining this so that people just go set their WORKON_HOME appropriately
in their login scripts or use a flag to mkvirtualenv telling it to put the
virtualenv in PYTHON_HOME (assuming such flag exists).

On Sunday, June 2, 2013, yarko wrote:

> In scripts/create-dev-env.sh:
>
> > @@ -406,14 +417,14 @@ fi
> >  # Create edX virtualenv and link it to repo
> >  # virtualenvwrapper automatically sources the activation script
> >  if [[ $systempkgs ]]; then
> > -    mkvirtualenv -a "$HOME/.virtualenvs" --system-site-packages edx-platform || {
>
> PYTHON_HOME is set to WORKON_HOME (or default) early on; by line 389,
> WORKON_HOME here is set to PYTHON_HOME.
>
> There is no reason to override WORKON_HOME setting by this point.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/edx/edx-platform/pull/38/files#r4491163>
> .
>


-- 
Nate