aws / aws/aws-elastic-beanstalk-cli-setup
C:\Users\karth>python --version
- Dominant language
- Python
- Stars
- 537
- Forks
- 226
- PR merge metrics
- No merged PRs in 30d
Description
C:\Users\karth>python --version
Python 3.7.4
C:\Users\karth>pip --version
pip 22.3.1 from C:\Users\karth\AppData\Roaming\Python\Python37\site-packages\pip (python 3.7)
C:\Users\karth>eb --version
failed to create process.
C:\Users\karth>pip freeze
awsebcli==3.20.3
botocore==1.23.54
cement==2.8.2
certifi==2022.12.7
charset-normalizer==2.0.12
colorama==0.4.3
future==0.16.0
idna==3.4
jmespath==0.10.0
pathspec==0.9.0
pypiwin32==223
python-dateutil==2.8.2
pywin32==305
PyYAML==5.4.1
requests==2.26.0
semantic-version==2.8.5
six==1.14.0
termcolor==1.1.0
urllib3==1.26.13
wcwidth==0.1.9
_Originally posted by @KarthikKalon in https://github.com/aws/aws-elastic-beanstalk-cli-setup/issues/136#issuecomment-1371798581_
Contributor guide
Research direction
Start by reproducing the Windows `eb --version` failure with the Python 3.7.4 and awsebcli 3.20.3 versions shown, then trace the `eb` installation entry point and process launcher. Done means the command runs successfully in the reported environment and the regression is covered by an appropriate test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- cloud, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100