You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 rvirtualenv.py directory from github version, shebang of generated scripts (myproj/bin/*.py )
is appropriate executable(it is my pythonbrew's python). But "rvirtualenv" command in "python setup.py install" version from same repository source also generated "#!/usr/bin/python2" shebang same as PYPI version.
OK: directly use rvirtualenv.py from respository source
INVALID: installed rvirtualenv command from same repository source
So I think the problem is occured in (root) setup.py of RVirtualEnv.
When I cut 'setuptools_dummy', line of setup_requires from root setup.py,
then installed "rvirtualenv" command generate appropriate shebang.
My tested python env is:
Python-2.7.2 installed by pythonbrew(it contains distribute and pip) on ubuntu amd64 11.04
Sincerely.
The text was updated successfully, but these errors were encountered:
Thanks for quick reply. I hope you fix PYPI uploaded version soon.
I think your design dicision is much better than tradisional virtualenv, especially to support growing site.py module.
I want to recommend RVirtualEnv instead of virtualenv, so it need to use with easy_install or pip install standard way.
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 rvirtualenv.py directory from github version, shebang of generated scripts (myproj/bin/*.py )
is appropriate executable(it is my pythonbrew's python). But "rvirtualenv" command in "python setup.py install" version from same repository source also generated "#!/usr/bin/python2" shebang same as PYPI version.
So I think the problem is occured in (root) setup.py of RVirtualEnv.
When I cut
'setuptools_dummy',
line ofsetup_requires
from root setup.py,then installed "rvirtualenv" command generate appropriate shebang.
My tested python env is:
Sincerely.
The text was updated successfully, but these errors were encountered: