aws-amplify / aws-amplify/amplify-cli
venv error message is incorrect
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 825
- Avg merge
- 11d 23h
- Merged PRs (30d)
- 2
Description
### How did you install the Amplify CLI?
npm
### If applicable, what version of Node.js are you using?
8.19.2
### Amplify CLI Version
12.8.2
### What operating system are you using?
Mac
### Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No
### Describe the bug
The following error message is incorrect. You can't install virtualenv by using `pip install venv`. venv has been built into python since python 3.3, so maybe that should be used instead.
https://docs.python.org/3/library/venv.html
If you want to use virtualenv instead, it can be installed with `pip install virtualenv`.
```You must have virtualenv installed and available on your PATH as "venv". It can be installed by running "pip3 install venv".```
### Expected behavior
Expecting to get a useful and accurate error message or none at all.
### Reproduction steps
1. Have Python installed, but without virtualenv on your system
2. Set up a Python API with the Amplify CLI https://docs.amplify.aws/guides/api-rest/python-api/q/platform/js/
4. Notice during `amplify push` step, that the inaccurate error message is displayed.
### Project Identifier
_No response_
### Log output
```
# Put your logs below this line
```
### Additional information
_No response_
### Before submitting, please confirm:
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
- [X] I have removed any sensitive information from my code snippets and submission.
Contributor guide
Research direction
Reproduce the problem by running `amplify push` for a Python API with Python installed but without virtualenv, then locate the source that emits the quoted message. Done means the CLI no longer recommends `pip3 install venv` and instead gives an accurate message or omits the error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, typescript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100