aws / aws/aws-elastic-beanstalk-cli-setup

Windows 10 ModuleNotFoundError: No module named 'virtualenv' Exiting due to failure

Open
#112 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
537
Forks
226
PR merge metrics
No merged PRs in 30d

Description

==============================================
II. Creating self-contained EBCLI installation
==============================================
Installing the EBCLI in C:\Users\me\.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:\Users\me\aws-elastic-beanstalk-cli-setup\scripts\virtualenv\bin\virtualenv.exe\__main__.py", line 5, in
ModuleNotFoundError: No module named 'virtualenv'
Exiting due to failure
PS C:\Users\me>

Contributor guide

Open the contributing guide

Research direction

Reproduce the EBCLI setup on Windows 10 with Python 3.7, then inspect the failing scripts/virtualenv/bin/virtualenv.exe/__main__.py entry point and the surrounding installer flow. 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, devops
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.