Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
bellbind opened this issue Jul 13, 2011 · 4 comments
Open
Assignees

Comments

@bellbind
Copy link

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.

@kvbik
Copy link
Owner

kvbik commented Jul 13, 2011

Good work, thanks for this issue!

It sounds more like a problem of setuptools_dummy, so I will probably remove them as a dependency (and fix setuptools_dummy later :)).

I hope this is why system-wide instalation of rvirtualenv (aka sudo python setup.py install) is broken now.

@ghost ghost assigned kvbik Jul 13, 2011
@bellbind
Copy link
Author

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.

@kvbik kvbik reopened this Jul 19, 2011
@kvbik
Copy link
Owner

kvbik commented Jul 19, 2011

i have some broken environment as well, so chasing the bug will be easier. hope i'll fix it pretty soon.

thx for you patience ;)

@kvbik
Copy link
Owner

kvbik commented Feb 5, 2012

ha, i have finally found the problem (and some time to fix it :)).

it is not about setuptools-dummy itself, but about adding some files during build time, that should be ignored

but i feel MANIFEST.in is better approach, so i'll try to switch!

kvbik added a commit that referenced this issue Feb 5, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants