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

can't build on a path containing spaces #334

Open
leehart opened this issue Jan 4, 2016 · 1 comment
Open

can't build on a path containing spaces #334

leehart opened this issue Jan 4, 2016 · 1 comment
Labels

Comments

@leehart
Copy link
Collaborator

leehart commented Jan 4, 2016

Could enquote paths in the build and run scripts, but then we'd still get "bad interpreter: No such file or directory" when build.sh attempts to use pip in virtual env.

@leehart leehart self-assigned this Jun 27, 2016
@leehart leehart added this to the 2.0.alpha5 milestone Jun 27, 2016
@leehart
Copy link
Collaborator Author

leehart commented Jun 30, 2016

pypa/virtualenv#53

http://stackoverflow.com/questions/15472430/using-virtualenv-with-spaces-in-a-path

pypa/pip#923

https://lists.gnu.org/archive/html/bug-bash/2008-05/msg00052.html

AlexeyMK's comment on pypa/pip#923 gives me hope that we might actually be able to work around this intractable issue (without forbidding spaces in path names) by using something like this in the build script:

python panoptes_virtualenv/bin/pip install -q -r REQUIREMENTS

instead of

pip install -q -r REQUIREMENTS

...but I suspect this kernel-deep limitation will keep on biting.

@leehart leehart modified the milestones: 2.0.alpha6, 2.0.alpha5 Jul 4, 2016
@leehart leehart removed this from the 2.0.alpha6 milestone Jul 5, 2016
@leehart leehart removed their assignment Dec 12, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants