-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
idna 3.0 version package conflict #5710
Comments
psf/requests#5710 This will be fixed upstream eventually, but for now it prevents Salt from working: pkg_resources.DistributionNotFound: The 'idna<3,>=2.5' distribution was not found and is required by requests Signed-off-by: Joe Groocock <me@frebib.net>
psf/requests#5710 This will be fixed upstream eventually, but for now it prevents Salt from working: pkg_resources.DistributionNotFound: The 'idna<3,>=2.5' distribution was not found and is required by requests Signed-off-by: Joe Groocock <me@frebib.net>
As "idna>=2.0.0", This causes
|
Workaround psf/requests#5710 as msys2 updated its python-idna package to 3.1
This conflict between |
@jace |
@sethmlarson
|
@sethmlarson how long do we have to keep using older version of |
Upgrading idna requires dropping python 2.7 so whenever that happens unless someone adds python_version markers to the dependancies |
@RhinosF1 There's already a pull request with version markers waiting for approval/merging #5711 - my hope is to have it merged into the next release but as the conversation about it been locked for contributors only (which being my first PR for requests I'm not yet are) I can't make sure that will happen. |
Didn't see that, thanks! |
The PR that fixes this and lets people use updated version of both packages has been blocked because this one entry might become a "maintenance nightmare" until |
@iambibhas That's not how I understood it, my understanding was that they are waiting for the next release for it and locked the conversation because they had too many people asking when it's due but I could be wrong |
@naorlivne apologies. You're right. I missed parts of the thread. Will keep an eye for the release. |
pip install idna==2.10 can't really install 2.10 |
|
My apologies; I was looking in the wrong place... I looked at only the download files for the headrev release, and not the page for the older 2.10 release. |
Version 2.05 works for me, but it's a bit annoying to get that error during build on Heroku. Any idea how I can ignore it? |
Workaround until `requests` stops breaking everyone's builds. psf/requests#5710
Workaround until `requests` stops breaking everyone's builds. psf/requests#5710
This has been blocking my update to latest idna for three months now (hartwork/wnpp.debian.net#13 (edit, and now hartwork/wnpp.debian.net#116)). |
This is needed, since the requests library does not yet support `idna > 2.x`. See this for information: psf/requests#5710 This shows up in Alpine containers during install as: ``` ERROR: Cannot install -r tests/integration/mender_integration/tests/requirements/python-requirements.txt (line 54) and idna==3.1 because these package versions have conflicting dependencies. The conflict is caused by: The user requested idna==3.1 requests 2.25.1 depends on idna<3 and >=2.5 ``` But not in containers with these dependencies already installed. Like this is from a `mender-qa` pipeline from a container running on the `docker` image: ``` Requirement already satisfied: idna==3.1 in /usr/lib/python3.8/site-packages (from -r /builds/Northern.tech/Mender/integration/tests/requirements/python-requirements.txt (line 23)) (3.1) Requirement already satisfied: requests==2.25.1 in /usr/lib/python3.8/site-packages (from -r /builds/Northern.tech/Mender/integration/tests/requirements/python-requirements.txt (line 54)) (2.25.1) ``` This is due to the installation in the `requirements/apk-requirements.txt` file, already installing this. Never the less, the requirements file is still wrong. Changelog: None Signed-off-by: Ole Petter <ole.orhagen@northern.tech>
This is needed, since the requests library does not yet support `idna > 2.x`. See this for information: psf/requests#5710 This shows up in Alpine containers during install as: ``` ERROR: Cannot install -r tests/integration/mender_integration/tests/requirements/python-requirements.txt (line 54) and idna==3.1 because these package versions have conflicting dependencies. The conflict is caused by: The user requested idna==3.1 requests 2.25.1 depends on idna<3 and >=2.5 ``` But not in containers with these dependencies already installed. Like this is from a `mender-qa` pipeline from a container running on the `docker` image: ``` Requirement already satisfied: idna==3.1 in /usr/lib/python3.8/site-packages (from -r /builds/Northern.tech/Mender/integration/tests/requirements/python-requirements.txt (line 23)) (3.1) Requirement already satisfied: requests==2.25.1 in /usr/lib/python3.8/site-packages (from -r /builds/Northern.tech/Mender/integration/tests/requirements/python-requirements.txt (line 54)) (2.25.1) ``` This is due to the installation in the `requirements/apk-requirements.txt` file, already installing this, in some cases: ``` �[32;1m$ apk add $(cat ${WORKSPACE}/integration/tests/requirements/apk-requirements.txt)�[0;m (1/73) Installing readline (8.1.0-r0) . . . (55/73) Installing py3-idna (3.1-r0) ``` Never the less, the requirements file is still wrong. Changelog: None Signed-off-by: Ole Petter <ole.orhagen@northern.tech>
This is needed, since the requests library does not yet support `idna > 2.x`. See this for information: psf/requests#5710 This shows up in Alpine containers during install as: ``` ERROR: Cannot install -r tests/integration/mender_integration/tests/requirements/python-requirements.txt (line 54) and idna==3.1 because these package versions have conflicting dependencies. The conflict is caused by: The user requested idna==3.1 requests 2.25.1 depends on idna<3 and >=2.5 ``` But not in containers with these dependencies already installed. Like this is from a `mender-qa` pipeline from a container running on the `docker` image: ``` Requirement already satisfied: idna==3.1 in /usr/lib/python3.8/site-packages (from -r /builds/Northern.tech/Mender/integration/tests/requirements/python-requirements.txt (line 23)) (3.1) Requirement already satisfied: requests==2.25.1 in /usr/lib/python3.8/site-packages (from -r /builds/Northern.tech/Mender/integration/tests/requirements/python-requirements.txt (line 54)) (2.25.1) ``` This is due to the installation in the `requirements/apk-requirements.txt` file, already installing this, in some cases: ``` �[32;1m$ apk add $(cat ${WORKSPACE}/integration/tests/requirements/apk-requirements.txt)�[0;m (1/73) Installing readline (8.1.0-r0) . . . (55/73) Installing py3-idna (3.1-r0) ``` Never the less, the requirements file is still wrong. Changelog: None Signed-off-by: Ole Petter <ole.orhagen@northern.tech> (cherry picked from commit 81a5b35) Signed-off-by: Ole Petter <ole.orhagen@northern.tech>
…t & requests can be resolved after psf/requests#5710 is fixed
…t & requests can be resolved after psf/requests#5710 is fixed
🙏 Is there an ETA for when #5711's patch goes into a PyPI release? |
idna released version 3.0 but requests has a dependency on idna<3, this makes it impossible to keep up to date on both packages.
Expected Result
I want to be able to install the latest idna package alongside the latest requests package
Actual Result
Reproduction Steps
try to run
pip install
on a requirements.txt file withSystem Information
multiple Python versions (3.6 up to 3.9) running on Docker containers inside Drone CI/CD
The text was updated successfully, but these errors were encountered: