chalice-local cannot find the Python interpreter from paths containing spaces

Nobody has claimed this yet.

I have installed chalice-local in a venv. Running `chalice-local deploy` gives me the following error:
`16:29 $ chalice-local deploy
-bash: /Users/bws/Documents/Work/Python Training/chalice-poc-rss/env/bin/chalice-local: /Users/bws/Documents/Work/Python: bad interpreter: No such file or directory`
You can see that it's considering the rest of the path (`Training/chalice...`) as a separate argument, so it's definitely the cause not passing explicitly as an argument array. I think I am going to open a PR on this.

Later edit: it's Chalice's issue

Reproduce `chalice-local deploy` from a virtual environment whose path contains spaces and inspect the reported `chalice-local` interpreter error. The issue's later edit identifies Chalice as the source, so confirm whether the fix belongs in this repository before making changes; done would mean the command works from such a path.

Written by the indexing model from the issue text.