Daniel Hahler 86046fd4e8 Do not allow whitespace in VIRTUALENV_NAME ...

While this could work in general, it fails in the end, because
whitespace is not allowed/supported in the shebang line with the
scripts in the created virtualenv.

2014-09-03 23:28:46 +02:00

..

stubs

Add unittest

2014-01-18 18:19:53 +09:00

tmp

Add .gitignore

2014-01-21 00:04:48 +09:00

activate.bats

Use . instead of source to support POSIX sh

2014-08-13 10:54:18 +09:00

deactivate.bats

Deactivate virtualenv even if it has been activated manually

2014-07-11 20:24:58 +09:00

hooks.bats

Workaround for the issue with pyenv-which-ext (refs #26)

2014-06-15 18:36:21 +09:00

init.bats

Indent to 2 spaces.

2014-08-13 19:51:22 +01:00

installer.bats

Add eval "$(pyenv virtualenv-init -)" to setup _precmd_ for user's shell

2014-06-04 15:24:12 +09:00

pip.bats

Use same _ensurepip_ logic as python-build

2014-06-28 00:49:04 +09:00

pyvenv.bats

Run _ensurepip_ after the every creation of virtualenv/pyvenv

2014-06-28 01:03:33 +09:00

test_helper.bash

Workaround for the issue with pyenv-which-ext (refs #26)

2014-06-15 18:36:21 +09:00

version.bats

v20140705

2014-07-05 17:26:53 +09:00

virtualenv-prefix.bats

Fix virtualenv-prefix when the version is system

2014-07-04 22:44:08 +09:00

virtualenv.bats

Do not allow whitespace in VIRTUALENV_NAME

2014-09-03 23:28:46 +02:00

virtualenvs.bats

Add tests for pyenv-virtualenvs

2014-01-23 15:14:01 +09:00