aws / aws/aws-elastic-beanstalk-cli-setup
ModuleNotFoundError: No module named 'virtualenv'
- Dominant language
- Python
- Stars
- 537
- Forks
- 226
- PR merge metrics
- No merged PRs in 30d
Description
**1. Please specify the following:**
- OS: Windows 10
- Shell (Bash, PowerShell, Zsh, etc.): cmd
**2. Description**
I executed the following 2 commands (without having Python 3.7.3 installed) in my **Command Prompt** on **Windows 10**:
```
git clone https://github.com/aws/aws-elastic-beanstalk-cli-setup.git
./aws-elastic-beanstalk-cli-setup/scripts/bundled_installer
```
After doing that I received the following error:
```
==============================================
II. Creating self-contained EBCLI installation
==============================================
Installing the EBCLI in C:\Users\bn\.ebcli-virtual-env
******************************************
1. Creating exclusive virtualenv for EBCLI
******************************************
Traceback (most recent call last):
File "c:\program files\python37\lib\runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
File "c:\program files\python37\lib\runpy.py", line 85, in _run_code
exec(code, run_globals)
File "C:\dev\env\aws-elastic-beanstalk-cli-setup\scripts\virtualenv\bin\virtualenv.exe\__main__.py", line 5, in
ModuleNotFoundError: No module named 'virtualenv'
Exiting due to failure
```
**Screenshot**

Contributor guide
Research direction
Start with scripts/bundled_installer and the bundled scripts/virtualenv/bin/virtualenv.exe entry point, then reproduce the reported installation on Windows 10 without Python 3.7.3 installed. Done means the self-contained EBCLI installation completes without the ModuleNotFoundError.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- cli, cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100