Issues

Issue #177 wontfix

I suggest to append "export -f ..." against all virtualenvwrapper.sh functions

Stéphane Klein
created an issue

Hi,

If I execute a script like https://github.com/nose-devs/nose2/blob/master/bootstrap.sh

bootstrap.sh content :

mkvirtualenv nose2
pip install -r requirements.txt
python setup.py develop

I've this error :

$ ./bootstrap.sh
./bootstrap.sh: line 7: mkvirtualenv: command not found

Now, if I append some "export -f" lines in virtualenvwrapper.sh like :

export -f mkvirtualenv
export -f mkproject
...

then bootstrap.sh work with success.

This is my virtualenvwrapper.sh : https://gist.github.com/harobed/66ce862ee0f86475b8dc

I've appended one "export -f" by function.

Unfortunately, virtualenvwrapper test don't work.

What do you think about my virtualenvwrapper.sh version ?

Comments (4)

  1. Doug Hellmann repo owner

    The preferred mode of use is to just source the wrapper script from the application that needs it. Otherwise the caller has to know to set up the wrappers before using the script. However, if the export syntax is portable, I could see including those changes.

  2. Log in to comment