-
Notifications
You must be signed in to change notification settings - Fork 78
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
Python 2 support broken with latest release of Pyrsistent #48
Comments
We're seeing this as well. It broke our automated elastic beanstalk deployments via Github Actions. Issue I think is that the latest 3 versions of Pyrsistent were yanked (https://pypi.org/project/pyrsistent/#history), but pip is not ignoring those yanked versions of Pyrsistent (see pypa/pip#8262 ?) and instead attempts to install the latest yanked 0.17.2 and fails instead of installing the last valid version 0.16.0. |
This hit us today as well. Apparently older versions of pip do not understand yanked packages, so they'll install them regardless. A workaround for now:
|
Actually I would prefer to use Python 3, but I cannot because of a |
Hi @baer are you still facing the issue ?I've recently checked the latest dependencies of awsebcli version 3.20.10, and I can confirm that pyrsistent is no longer a dependency . Can you please recheck and confirm if you are still facing the issue ? |
@NihalM99 I do not work in that codebase anymore, so I can't verify. However, if it's no longer a dep, this issue should get closed out. |
We have dropped support for Python 2.7 since it is deprecated. |
Description
Python 2 support is broken.
In release 17.1, the ebcli dependency Pyrsistent drops support for Python 2.x. This project, as with the AWS-SDK, supports both Python 2.7+ and 3.4+.
Steps to reproduce
I ran into this in a CI environment that runs Debian Buster. Specifically, the
node:lts-buster
Docker image. To reproduce, you can run the following commands:Observed result
The failure happens while deps are being resolved. Happy to provide more info if needed.
The text was updated successfully, but these errors were encountered: