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

Open
#8 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
cli

Research direction

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.

Description

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

Dominant language
Python
Stars
21
Forks
3
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from localstack/chalice-local

All issues in localstack/chalice-local

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.