rvirtualenv

rvirtualenv copied to clipboard

- test dependencies (at leas `requirements`) - rename `tests` dir to `test_rvirtualenv` - add to MANIFEST.in and be sure it will not get installed to system

kvbik

because virtualenv itself can be read-only for some user see https://github.com/kvbik/rvirtualenv/blob/master/rvirtualenv/template/inst/bin/activate maybe use python for guessing location of activate script?

kvbik

at least it does on windows 7 box steps to reproduce in cmd.exe: - clone latest master of rvirtualenv - `C:\rvirtualenv> rvirtualenv.py NEWENV` - `C:\rvirtualenv> NEWENV\bin\activate.bat` - `C:\rvirtualenv> python` now...

kvbik

setuptools_dummy generate scripts with fixed shebang #!/usr/bin/python2

4

PYPI packaged version of RVirtualEnv (0.3.1) always generate scripts(proj/bin/*.py ) with shebang #!/usr/bin/python2 ,which executable is not in the system, with or without --python option. When I try to use...

bellbind

Karamel911

Karamel911