===========================================================
.___ __ __
_________________ __ __ __| _/|__|/ |_
/ ___\_` __ \__ \ | | \/ __ | | \\_ __\
/ /_/ > | \// __ \| | / /_/ | | || |
\___ /|__| (____ /____/\____ | |__||__|
/_____/ \/ \/
grep rough audit - static analysis tool
v2.8 written by @Wireghoul
=================================[justanotherhacker.com]===
virtualenvwrapper-4.8.4/docs/source/install.rst-138-directly, use ``virtualenvwrapper_lazy.sh``. If
virtualenvwrapper-4.8.4/docs/source/install.rst:139:``virtualenvwrapper.sh`` is not on your ``$PATH``, set
virtualenvwrapper-4.8.4/docs/source/install.rst-140-``VIRTUALENVWRAPPER_SCRIPT`` to point to it.
##############################################
virtualenvwrapper-4.8.4/docs/source/install.rst-179-The variable ``WORKON_HOME`` tells virtualenvwrapper where to place
virtualenvwrapper-4.8.4/docs/source/install.rst:180:your virtual environments. The default is ``$HOME/.virtualenvs``. If
virtualenvwrapper-4.8.4/docs/source/install.rst-181-the directory does not exist when virtualenvwrapper is loaded, it will
##############################################
virtualenvwrapper-4.8.4/docs/source/install.rst-230-where the :ref:`user-defined hooks <scripts>` should be placed. The
virtualenvwrapper-4.8.4/docs/source/install.rst:231:default is ``$WORKON_HOME``.
virtualenvwrapper-4.8.4/docs/source/install.rst-232-
##############################################
virtualenvwrapper-4.8.4/docs/source/install.rst-255-During startup, ``virtualenvwrapper.sh`` finds the first ``python``
virtualenvwrapper-4.8.4/docs/source/install.rst:256:and ``virtualenv`` programs on the ``$PATH`` and remembers them to use
virtualenvwrapper-4.8.4/docs/source/install.rst:257:later. This eliminates any conflict as the ``$PATH`` changes,
virtualenvwrapper-4.8.4/docs/source/install.rst-258-enabling interpreters inside virtual environments where
##############################################
virtualenvwrapper-4.8.4/docs/source/install.rst-260-virtualenv are installed. Because of this behavior, it is important
virtualenvwrapper-4.8.4/docs/source/install.rst:261:for the ``$PATH`` to be set **before** sourcing
virtualenvwrapper-4.8.4/docs/source/install.rst-262-``virtualenvwrapper.sh``. For example::
##############################################
virtualenvwrapper-4.8.4/docs/source/install.rst-266-
virtualenvwrapper-4.8.4/docs/source/install.rst:267:To override the ``$PATH`` search, set the variable
virtualenvwrapper-4.8.4/docs/source/install.rst-268-``VIRTUALENVWRAPPER_PYTHON`` to the full path of the interpreter to
##############################################
virtualenvwrapper-4.8.4/docs/source/install.rst-293-
virtualenvwrapper-4.8.4/docs/source/install.rst:294:virtualenvwrapper creates temporary files in ``$TMPDIR``. If the
virtualenvwrapper-4.8.4/docs/source/install.rst-295-variable is not set, it uses ``/tmp``. To change the location of
##############################################
virtualenvwrapper-4.8.4/docs/source/command_ref.rst-350-
virtualenvwrapper-4.8.4/docs/source/command_ref.rst:351:Change the current working directory to ``$VIRTUAL_ENV``.
virtualenvwrapper-4.8.4/docs/source/command_ref.rst-352-
##############################################
virtualenvwrapper-4.8.4/docs/source/command_ref.rst-357-Calling ``cdvirtualenv`` changes the current working directory to the
virtualenvwrapper-4.8.4/docs/source/command_ref.rst:358:top of the virtualenv (``$VIRTUAL_ENV``). An optional argument is
virtualenvwrapper-4.8.4/docs/source/command_ref.rst-359-appended to the path, allowing navigation directly into a
##############################################
virtualenvwrapper-4.8.4/docs/source/command_ref.rst-382-Change the current working directory to the ``site-packages`` for
virtualenvwrapper-4.8.4/docs/source/command_ref.rst:383:``$VIRTUAL_ENV``.
virtualenvwrapper-4.8.4/docs/source/command_ref.rst-384-
##############################################
virtualenvwrapper-4.8.4/docs/source/tips.rst-17-
virtualenvwrapper-4.8.4/docs/source/tips.rst:18:Using zsh, I added some bits to ``$WORKON_HOME/post(de)activate`` to show
virtualenvwrapper-4.8.4/docs/source/tips.rst-19-the active virtualenv on the right side of my screen instead.
##############################################
virtualenvwrapper-4.8.4/docs/source/tips.rst-24- _OLD_RPROMPT="$RPROMPT"
virtualenvwrapper-4.8.4/docs/source/tips.rst:25: RPROMPT="%{${fg_bold[white]}%}(env: %{${fg[green]}%}`basename \"$VIRTUAL_ENV\"`%{${fg_bold[white]}%})%{${reset_color}%} $RPROMPT"
virtualenvwrapper-4.8.4/docs/source/tips.rst-26-
##############################################
virtualenvwrapper-4.8.4/docs/source/tips.rst-32-
virtualenvwrapper-4.8.4/docs/source/tips.rst:33:Updating cached ``$PATH`` entries
virtualenvwrapper-4.8.4/docs/source/tips.rst-34-=================================
##############################################
virtualenvwrapper-4.8.4/docs/source/tips.rst-37-
virtualenvwrapper-4.8.4/docs/source/tips.rst:38:I also added the command 'rehash' to ``$WORKON_HOME/postactivate`` and
virtualenvwrapper-4.8.4/docs/source/tips.rst:39:``$WORKON_HOME/postdeactivate`` as I was having some problems with zsh
virtualenvwrapper-4.8.4/docs/source/tips.rst-40-not picking up the new paths immediately.
##############################################
virtualenvwrapper-4.8.4/docs/source/plugins.rst-237-The hook loader configures logging so that messages are written to
virtualenvwrapper-4.8.4/docs/source/plugins.rst:238:``$WORKON_HOME/hook.log``. Messages also may be written to stderr,
virtualenvwrapper-4.8.4/docs/source/plugins.rst-239-depending on the verbosity flag. The default is for messages at *info*
##############################################
virtualenvwrapper-4.8.4/docs/source/plugins.rst-304-activated. The current working directory for when the hook is run is
virtualenvwrapper-4.8.4/docs/source/plugins.rst:305:``$WORKON_HOME`` and the name of the new environment is passed as an
virtualenvwrapper-4.8.4/docs/source/plugins.rst-306-argument.
##############################################
virtualenvwrapper-4.8.4/docs/source/plugins.rst-313-The ``virtualenvwrapper.post_mkvirtualenv`` hooks are run after a new
virtualenvwrapper-4.8.4/docs/source/plugins.rst:314:virtual environment is created and activated. ``$VIRTUAL_ENV`` is set
virtualenvwrapper-4.8.4/docs/source/plugins.rst-315-to point to the new environment.
##############################################
virtualenvwrapper-4.8.4/docs/source/plugins.rst-331-The ``virtualenvwrapper.post_activate`` hooks are run just after an
virtualenvwrapper-4.8.4/docs/source/plugins.rst:332:environment is enabled. ``$VIRTUAL_ENV`` is set to point to the
virtualenvwrapper-4.8.4/docs/source/plugins.rst-333-current environment.
##############################################
virtualenvwrapper-4.8.4/docs/source/plugins.rst-340-The ``virtualenvwrapper.pre_deactivate`` hooks are run just before an
virtualenvwrapper-4.8.4/docs/source/plugins.rst:341:environment is disabled. ``$VIRTUAL_ENV`` is set to point to the
virtualenvwrapper-4.8.4/docs/source/plugins.rst-342-current environment.
##############################################
virtualenvwrapper-4.8.4/docs/source/scripts.rst-44-
virtualenvwrapper-4.8.4/docs/source/scripts.rst:45:``$VIRTUALENVWRAPPER_HOOK_DIR/get_env_details`` is run when ``workon`` is run with no
virtualenvwrapper-4.8.4/docs/source/scripts.rst-46-arguments and a list of the virtual environments is printed. The hook
##############################################
virtualenvwrapper-4.8.4/docs/source/scripts.rst-58-
virtualenvwrapper-4.8.4/docs/source/scripts.rst:59:``$VIRTUALENVWRAPPER_HOOK_DIR/initialize`` is sourced when ``virtualenvwrapper.sh``
virtualenvwrapper-4.8.4/docs/source/scripts.rst-60-is loaded into your environment. Use it to adjust global settings
##############################################
virtualenvwrapper-4.8.4/docs/source/scripts.rst-71-
virtualenvwrapper-4.8.4/docs/source/scripts.rst:72:``$VIRTUALENVWRAPPER_HOOK_DIR/premkvirtualenv`` is run as an external program after
virtualenvwrapper-4.8.4/docs/source/scripts.rst-73-the virtual environment is created but before the current environment
virtualenvwrapper-4.8.4/docs/source/scripts.rst-74-is switched to point to the new env. The current working directory for
virtualenvwrapper-4.8.4/docs/source/scripts.rst:75:the script is ``$WORKON_HOME`` and the name of the new environment is
virtualenvwrapper-4.8.4/docs/source/scripts.rst-76-passed as an argument to the script.
##############################################
virtualenvwrapper-4.8.4/docs/source/scripts.rst-86-
virtualenvwrapper-4.8.4/docs/source/scripts.rst:87:``$VIRTUALENVWRAPPER_HOOK_DIR/postmkvirtualenv`` is sourced after the new environment
virtualenvwrapper-4.8.4/docs/source/scripts.rst-88-is created and activated. If the ``-a`` <project_path> flag was used,
##############################################
virtualenvwrapper-4.8.4/docs/source/scripts.rst-99-
virtualenvwrapper-4.8.4/docs/source/scripts.rst:100:``$VIRTUALENVWRAPPER_HOOK_DIR/precpvirtualenv`` is run as an external program after
virtualenvwrapper-4.8.4/docs/source/scripts.rst-101-the source environment is duplicated and made relocatable, but before
##############################################
virtualenvwrapper-4.8.4/docs/source/scripts.rst-103-switched to point to the new env. The current working directory for
virtualenvwrapper-4.8.4/docs/source/scripts.rst:104:the script is ``$WORKON_HOME`` and the names of the source and new
virtualenvwrapper-4.8.4/docs/source/scripts.rst-105-environments are passed as arguments to the script.
##############################################
virtualenvwrapper-4.8.4/docs/source/scripts.rst-115-
virtualenvwrapper-4.8.4/docs/source/scripts.rst:116:``$VIRTUALENVWRAPPER_HOOK_DIR/postcpvirtualenv`` is sourced after the new environment
virtualenvwrapper-4.8.4/docs/source/scripts.rst-117-is created and activated.
##############################################
virtualenvwrapper-4.8.4/docs/source/scripts.rst-127-
virtualenvwrapper-4.8.4/docs/source/scripts.rst:128:The global ``$VIRTUALENVWRAPPER_HOOK_DIR/preactivate`` script is run before the new
virtualenvwrapper-4.8.4/docs/source/scripts.rst-129-environment is enabled. The environment name is passed as the first
##############################################
virtualenvwrapper-4.8.4/docs/source/scripts.rst-131-
virtualenvwrapper-4.8.4/docs/source/scripts.rst:132:The local ``$VIRTUAL_ENV/bin/preactivate`` hook is run before the new
virtualenvwrapper-4.8.4/docs/source/scripts.rst-133-environment is enabled. The environment name is passed as the first
##############################################
virtualenvwrapper-4.8.4/docs/source/scripts.rst-144-
virtualenvwrapper-4.8.4/docs/source/scripts.rst:145:The global ``$VIRTUALENVWRAPPER_HOOK_DIR/postactivate`` script is sourced after the
virtualenvwrapper-4.8.4/docs/source/scripts.rst:146:new environment is enabled. ``$VIRTUAL_ENV`` refers to the new
virtualenvwrapper-4.8.4/docs/source/scripts.rst-147-environment at the time the script runs.
##############################################
virtualenvwrapper-4.8.4/docs/source/scripts.rst-153-
virtualenvwrapper-4.8.4/docs/source/scripts.rst:154: PS1="(`basename \"$VIRTUAL_ENV\"`) $_OLD_VIRTUAL_PS1"
virtualenvwrapper-4.8.4/docs/source/scripts.rst-155-
virtualenvwrapper-4.8.4/docs/source/scripts.rst:156:The local ``$VIRTUAL_ENV/bin/postactivate`` script is sourced after
virtualenvwrapper-4.8.4/docs/source/scripts.rst:157:the new environment is enabled. ``$VIRTUAL_ENV`` refers to the new
virtualenvwrapper-4.8.4/docs/source/scripts.rst-158-environment at the time the script runs.
##############################################
virtualenvwrapper-4.8.4/docs/source/scripts.rst-178-
virtualenvwrapper-4.8.4/docs/source/scripts.rst:179:The local ``$VIRTUAL_ENV/bin/predeactivate`` script is sourced before the
virtualenvwrapper-4.8.4/docs/source/scripts.rst-180-current environment is deactivated, and can be used to disable or
virtualenvwrapper-4.8.4/docs/source/scripts.rst:181:clear settings in your environment. ``$VIRTUAL_ENV`` refers to the old
virtualenvwrapper-4.8.4/docs/source/scripts.rst-182-environment at the time the script runs.
virtualenvwrapper-4.8.4/docs/source/scripts.rst-183-
virtualenvwrapper-4.8.4/docs/source/scripts.rst:184:The global ``$VIRTUALENVWRAPPER_HOOK_DIR/predeactivate`` script is sourced before the
virtualenvwrapper-4.8.4/docs/source/scripts.rst:185:current environment is deactivated. ``$VIRTUAL_ENV`` refers to the
virtualenvwrapper-4.8.4/docs/source/scripts.rst-186-old environment at the time the script runs.
##############################################
virtualenvwrapper-4.8.4/docs/source/scripts.rst-196-
virtualenvwrapper-4.8.4/docs/source/scripts.rst:197:The ``$VIRTUAL_ENV/bin/postdeactivate`` script is sourced after the
virtualenvwrapper-4.8.4/docs/source/scripts.rst-198-current environment is deactivated, and can be used to disable or
virtualenvwrapper-4.8.4/docs/source/scripts.rst-199-clear settings in your environment. The path to the environment just
virtualenvwrapper-4.8.4/docs/source/scripts.rst:200:deactivated is available in ``$VIRTUALENVWRAPPER_LAST_VIRTUALENV``.
virtualenvwrapper-4.8.4/docs/source/scripts.rst-201-
##############################################
virtualenvwrapper-4.8.4/docs/source/scripts.rst-210-
virtualenvwrapper-4.8.4/docs/source/scripts.rst:211:The ``$VIRTUALENVWRAPPER_HOOK_DIR/prermvirtualenv`` script is run as an external
virtualenvwrapper-4.8.4/docs/source/scripts.rst-212-program before the environment is removed. The full path to the
##############################################
virtualenvwrapper-4.8.4/docs/source/scripts.rst-223-
virtualenvwrapper-4.8.4/docs/source/scripts.rst:224:The ``$VIRTUALENVWRAPPER_HOOK_DIR/postrmvirtualenv`` script is run as an external
virtualenvwrapper-4.8.4/docs/source/scripts.rst-225-program after the environment is removed. The full path to the
##############################################
virtualenvwrapper-4.8.4/docs/source/scripts.rst-236-
virtualenvwrapper-4.8.4/docs/source/scripts.rst:237:``$WORKON_HOME/premkproject`` is run as an external program after the
virtualenvwrapper-4.8.4/docs/source/scripts.rst-238-virtual environment is created and after the current environment is
##############################################
virtualenvwrapper-4.8.4/docs/source/scripts.rst-240-is created. The current working directory for the script is
virtualenvwrapper-4.8.4/docs/source/scripts.rst:241:``$PROJECT_HOME`` and the name of the new project is passed as an
virtualenvwrapper-4.8.4/docs/source/scripts.rst-242-argument to the script.
##############################################
virtualenvwrapper-4.8.4/docs/source/scripts.rst-252-
virtualenvwrapper-4.8.4/docs/source/scripts.rst:253:``$WORKON_HOME/postmkproject`` is sourced after the new environment
virtualenvwrapper-4.8.4/docs/source/scripts.rst-254-and project directories are created and the virtualenv is activated.
##############################################
virtualenvwrapper-4.8.4/docs/source/developers.rst-110-created. The current working directory is the directory created to
virtualenvwrapper-4.8.4/docs/source/developers.rst:111:hold the project files (``$PROJECT_HOME/$envname``).
virtualenvwrapper-4.8.4/docs/source/developers.rst-112-
##############################################
virtualenvwrapper-4.8.4/tests/test_add2virtualenv.sh-83- path_file="./_virtualenv_path_extensions.pth"
virtualenvwrapper-4.8.4/tests/test_add2virtualenv.sh:84: assertTrue "No $parent_dir/$base_dir in \"`cat $path_file`\"" "grep -q \"$parent_dir/$base_dir\" $path_file"
virtualenvwrapper-4.8.4/tests/test_add2virtualenv.sh-85- cd - >/dev/null 2>&1
##############################################
virtualenvwrapper-4.8.4/tests/test_add2virtualenv.sh-96- path_file="./_virtualenv_path_extensions.pth"
virtualenvwrapper-4.8.4/tests/test_add2virtualenv.sh:97: assertTrue "No 'a b' in \"`cat $path_file`\"" "grep -q 'a b' $path_file"
virtualenvwrapper-4.8.4/tests/test_add2virtualenv.sh-98- cd - >/dev/null 2>&1
##############################################
virtualenvwrapper-4.8.4/tests/test_add2virtualenv.sh-109- path_file="./_virtualenv_path_extensions.pth"
virtualenvwrapper-4.8.4/tests/test_add2virtualenv.sh:110: assertTrue "No 'a & b' in \"`cat $path_file`\"" "grep -q 'a & b' $path_file"
virtualenvwrapper-4.8.4/tests/test_add2virtualenv.sh-111- cd - >/dev/null 2>&1
##############################################
virtualenvwrapper-4.8.4/tests/test_add2virtualenv.sh-122- add2virtualenv -d "/full/path"
virtualenvwrapper-4.8.4/tests/test_add2virtualenv.sh:123: assertFalse "/full/path in `cat $path_file`" "grep -q /full/path $path_file"
virtualenvwrapper-4.8.4/tests/test_add2virtualenv.sh-124- cd - >/dev/null 2>&1
##############################################
virtualenvwrapper-4.8.4/tests/test_add2virtualenv.sh-135- add2virtualenv -d "/full/path with spaces"
virtualenvwrapper-4.8.4/tests/test_add2virtualenv.sh:136: assertFalse "/full/path with spaces in `cat $path_file`" "grep -q '/full/path with spaces' $path_file"
virtualenvwrapper-4.8.4/tests/test_add2virtualenv.sh-137- cd - >/dev/null 2>&1
##############################################
virtualenvwrapper-4.8.4/tests/test_add2virtualenv.sh-148- add2virtualenv -d "/full/path & dir"
virtualenvwrapper-4.8.4/tests/test_add2virtualenv.sh:149: assertFalse "/full/path & dir in `cat $path_file`" "grep -q '/full/path & dir' $path_file"
virtualenvwrapper-4.8.4/tests/test_add2virtualenv.sh-150- cd - >/dev/null 2>&1
##############################################
virtualenvwrapper-4.8.4/tests/shunit2-401- # see if condition is an integer, i.e. a return value
virtualenvwrapper-4.8.4/tests/shunit2:402: shunit_match_=`expr "${shunit_condition_}" : '\([0-9]*\)'`
virtualenvwrapper-4.8.4/tests/shunit2-403- shunit_return=${SHUNIT_TRUE}
##############################################
virtualenvwrapper-4.8.4/tests/shunit2-471- # see if condition is an integer, i.e. a return value
virtualenvwrapper-4.8.4/tests/shunit2:472: shunit_match_=`expr "${shunit_condition_}" : '\([0-9]*\)'`
virtualenvwrapper-4.8.4/tests/shunit2-473- shunit_return=${SHUNIT_TRUE}
##############################################
virtualenvwrapper-4.8.4/tests/shunit2-785- __shunit_suite="${__shunit_suite:+${__shunit_suite} }${shunit_func_}"
virtualenvwrapper-4.8.4/tests/shunit2:786: __shunit_testsTotal=`expr ${__shunit_testsTotal} + 1`
virtualenvwrapper-4.8.4/tests/shunit2-787-
##############################################
virtualenvwrapper-4.8.4/tests/shunit2-898- _shunit_date_=`date '+%Y%m%d%H%M%S'`
virtualenvwrapper-4.8.4/tests/shunit2:899: _shunit_random_=`expr ${_shunit_date_} / $$`
virtualenvwrapper-4.8.4/tests/shunit2-900- fi
##############################################
virtualenvwrapper-4.8.4/tests/shunit2-949- # add 128 to signal and exit
virtualenvwrapper-4.8.4/tests/shunit2:950: exit `expr ${_shunit_signal_} + 128`
virtualenvwrapper-4.8.4/tests/shunit2-951- elif [ ${__shunit_reportGenerated} -eq ${SHUNIT_FALSE} ] ; then
##############################################
virtualenvwrapper-4.8.4/tests/shunit2-980- if [ ${__shunit_testSuccess} -eq ${SHUNIT_TRUE} ]; then
virtualenvwrapper-4.8.4/tests/shunit2:981: __shunit_testsPassed=`expr ${__shunit_testsPassed} + 1`
virtualenvwrapper-4.8.4/tests/shunit2-982- else
virtualenvwrapper-4.8.4/tests/shunit2:983: __shunit_testsFailed=`expr ${__shunit_testsFailed} + 1`
virtualenvwrapper-4.8.4/tests/shunit2-984- fi
##############################################
virtualenvwrapper-4.8.4/tests/shunit2-1040-{
virtualenvwrapper-4.8.4/tests/shunit2:1041: __shunit_assertsPassed=`expr ${__shunit_assertsPassed} + 1`
virtualenvwrapper-4.8.4/tests/shunit2:1042: __shunit_assertsTotal=`expr ${__shunit_assertsTotal} + 1`
virtualenvwrapper-4.8.4/tests/shunit2-1043-}
##############################################
virtualenvwrapper-4.8.4/tests/shunit2-1049- __shunit_testSuccess=${SHUNIT_FALSE}
virtualenvwrapper-4.8.4/tests/shunit2:1050: __shunit_assertsFailed=`expr ${__shunit_assertsFailed} + 1`
virtualenvwrapper-4.8.4/tests/shunit2:1051: __shunit_assertsTotal=`expr ${__shunit_assertsTotal} + 1`
virtualenvwrapper-4.8.4/tests/shunit2-1052- echo "${__SHUNIT_ASSERT_MSG_PREFIX}${_shunit_msg_}"
##############################################
virtualenvwrapper-4.8.4/tests/shunit2-1058-{
virtualenvwrapper-4.8.4/tests/shunit2:1059: __shunit_assertsSkipped=`expr ${__shunit_assertsSkipped} + 1`
virtualenvwrapper-4.8.4/tests/shunit2:1060: __shunit_assertsTotal=`expr ${__shunit_assertsTotal} + 1`
virtualenvwrapper-4.8.4/tests/shunit2-1061-}
##############################################
virtualenvwrapper-4.8.4/README.txt-15-changes for extensions from 3.x. The python modules for extensions are
virtualenvwrapper-4.8.4/README.txt:16:now *always* run with ``PWD=$WORKON_HOME`` (previously the value of
virtualenvwrapper-4.8.4/README.txt-17-PWD varied depending on the hook). The *shell* portion of any hook
##############################################
virtualenvwrapper-4.8.4/PKG-INFO-23- changes for extensions from 3.x. The python modules for extensions are
virtualenvwrapper-4.8.4/PKG-INFO:24: now *always* run with ``PWD=$WORKON_HOME`` (previously the value of
virtualenvwrapper-4.8.4/PKG-INFO-25- PWD varied depending on the hook). The *shell* portion of any hook
##############################################
virtualenvwrapper-4.8.4/.pc/remove-virtualenvwrapper_lazy-shebang.patch/virtualenvwrapper_lazy.sh-22- # NOTE: For Zsh, I have tried to unset any auto-load completion.
virtualenvwrapper-4.8.4/.pc/remove-virtualenvwrapper_lazy-shebang.patch/virtualenvwrapper_lazy.sh:23: # (via `compctl + $(echo ${_VIRTUALENVWRAPPER_API})`.
virtualenvwrapper-4.8.4/.pc/remove-virtualenvwrapper_lazy-shebang.patch/virtualenvwrapper_lazy.sh-24- # But this does not appear to work / triggers a crash.
##############################################
virtualenvwrapper-4.8.4/virtualenvwrapper_lazy.sh-21- # NOTE: For Zsh, I have tried to unset any auto-load completion.
virtualenvwrapper-4.8.4/virtualenvwrapper_lazy.sh:22: # (via `compctl + $(echo ${_VIRTUALENVWRAPPER_API})`.
virtualenvwrapper-4.8.4/virtualenvwrapper_lazy.sh-23- # But this does not appear to work / triggers a crash.