-
Notifications
You must be signed in to change notification settings - Fork 227
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EB CLI Installer error: "Getting requirements to build wheel ... error" #148
Comments
I've found a few other projects with the same issue
It appears to be due to the new major version of Cython which was released on the 17th of July 2023 - https://pypi.org/project/Cython/#history |
I have the same issue. It seems that this error broke our deploy process in GitHub Actions. The latest successful deploy was on July 14 and since than we have a number of updates:
You can replicate it in docker:
In container:
Here's the log:
I tried to install virtualenv 20.23.1 ( |
I got the same issue with you. But I resolved it by downgrade from python 3.10 to 3.8 |
The problem has to do with version of |
Same error, Please post the quick fix for this |
@jdvin's suggestion worked for me as a work around until the issue is resolved. Using a container created from a Python image
Using a container created from a Debian image
|
Pleeeeeese fix this! I am not that experienced with python or virtualenv and I'm just running this install script as part of a CI/CD build. I cannot get any of the workarounds to work for me! |
I did actually get this working by following @jdvin's steps. |
I installed it using |
downgrading python to 3.7.17 and then running ebcli_installer worked for me. |
I get the same issue here. While the work around is valid, the installation uses There was a similar issue with the
They resolved this issue by extending support to |
I was able to fix this by adding |
hoping awsebcli can be updated ASAP, becoming compliant with PyYAML == 6.0 currently the awsebcli crashes on installation. workarounds require downgrades to PyYAML (not acceptable in my situation) |
@Modulariz thank you. Your quick fix works. |
3 weeks without any fix in sight? 😬 |
I have left feedback at https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/eb-cli3-install.html since it refers people to this installation process which obviously does not work, maybe someone from AWS could update that page so folks don't waste their time. |
https://github.com/aws/aws-elastic-beanstalk-cli/blob/master/CHANGES.rst#32010-2023-09-15 But not published to PyPi yet. |
This is an error in PyYAML, caused by an upgrade to Cython 3.0 (see here). I fixed it by downgrading my installation of PyYAML
|
Thanks @hex-spell , this is the only solution that worked for me. Right on brother! |
I've written a Note that since this command has a hard-coded line number, it can break if the sed -i "558i\ '--no-build-isolation'," /tmp/aws-elastic-beanstalk-cli-setup/scripts/ebcli_installer.py |
customize the EB CLI installation using a modified action from install-eb-cli-action[1] to work around issue aws/aws-elastic-beanstalk-cli-setup#148 The idea is to install a specific version of python with a specific version of EB CLI to make a compatible pair. [1] https://github.com/sparkplug-app/install-eb-cli-action
attempt to fix ebcli by installing a specific version of pyyaml[1] [1] aws/aws-elastic-beanstalk-cli-setup#148 (comment)
attempt to fix ebcli by installing a specific version of pyyaml[1] [1] aws/aws-elastic-beanstalk-cli-setup#148 (comment)
Installation of EB CLI failed, we try to switch to installing from pypi with the workaround suggestion from aws/aws-elastic-beanstalk-cli-setup#148 (comment)
Installation of EB CLI failed, we try to switch to installing from pypi with the workaround suggestion from aws/aws-elastic-beanstalk-cli-setup#148 (comment)
1. Please specify the following:
2. Description
I am getting the following error when running the EB CLI Installer in a Docker container running Debian 12 (bookworm) with Python 3.11.2 "Getting requirements to build wheel ... error"
It was working fine 10 days ago but when I attempted to install it today I am unable to.
The full output is:
created virtual environment CPython3.11.2.final.0-64 in 265ms
creator CPython3Posix(dest=/root/.ebcli-virtual-env, clear=False, no_vcs_ignore=False, global=False)
seeder FromAppData(download=False, pip=bundle, setuptools=bundle, wheel=bundle, via=copy, app_data_dir=/root/.local/share/virtualenv)
added seed packages: pip==23.0.1, setuptools==66.1.1, wheel==0.38.4
activators BashActivator,CShellActivator,FishActivator,NushellActivator,PowerShellActivator,PythonActivator
Collecting awsebcli
Using cached awsebcli-3.20.7.tar.gz (267 kB)
Preparing metadata (setup.py) ... done
Collecting PyYAML<5.5,>=5.3.1
Using cached PyYAML-5.4.1.tar.gz (175 kB)
Installing build dependencies ... done
Getting requirements to build wheel ... error
error: subprocess-exited-with-error
× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> [68 lines of output]
/tmp/pip-build-env-1lg0xzzk/overlay/lib/python3.11/site-packages/setuptools/config/setupcfg.py:293: _DeprecatedConfig: Deprecated config in
setup.cfg
!!
note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error
× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.
The text was updated successfully, but these errors were encountered: