requests: idna 3.0 version package conflict
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
ERROR: Cannot install -r requirements.txt (line 12) and idna==3.0 because these package versions have conflicting dependencies.
The conflict is caused by:
The user requested idna==3.0
requests 2.25.1 depends on idna<3 and >=2.5
Reproduction Steps
try to run pip install on a requirements.txt file with
requests==2.25.1
idna==3.0
System Information
multiple Python versions (3.6 up to 3.9) running on Docker containers inside Drone CI/CD
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 88
- Comments: 20 (8 by maintainers)
Commits related to this issue
- Temporarily patch py3-requests idna dependency https://github.com/psf/requests/issues/5710 This will be fixed upstream eventually, but for now it prevents Salt from working: pkg_resources.Distr... — committed to frebib/salt-master by frebib 3 years ago
- Temporarily patch py3-requests idna dependency https://github.com/psf/requests/issues/5710 This will be fixed upstream eventually, but for now it prevents Salt from working: pkg_resources.Distr... — committed to frebib/salt-master by frebib 3 years ago
- appveyor/msys2: Install sphinx using pip Workaround https://github.com/psf/requests/issues/5710 as msys2 updated its python-idna package to 3.1 — committed to anlambert/talipot by anlambert 3 years ago
- Fix dependency problem from https://github.com/psf/requests/issues/5710 — committed to ssl-hep/ServiceX_frontend by BenGalewsky 3 years ago
- Fix dependency problem from https://github.com/psf/requests/issues/5710 — committed to ssl-hep/ServiceX_frontend by BenGalewsky 3 years ago
- Fix idna 3.1 is installed but idna<3,>=2.5 is required by {'requests'} error — committed to ccxt/ccxt by carlosmiei 3 years ago
- Temporarily "downgrade" idna Workaround until `requests` stops breaking everyone's builds. https://github.com/psf/requests/issues/5710 — committed to hasgeek/funnel by jace 3 years ago
- Temporarily "downgrade" idna (#1063) Workaround until `requests` stops breaking everyone's builds. https://github.com/psf/requests/issues/5710 — committed to hasgeek/funnel by jace 3 years ago
- [requirements.txt]: Downgrade idna to < 3.0 This is needed, since the requests library does not yet support `idna > 2.x`. See this for information: https://github.com/psf/requests/issues/5710 This... — committed to oleorhagen/integration by deleted user 3 years ago
- [requirements.txt]: Downgrade idna to < 3.0 This is needed, since the requests library does not yet support `idna > 2.x`. See this for information: https://github.com/psf/requests/issues/5710 This... — committed to oleorhagen/integration by deleted user 3 years ago
- [requirements.txt]: Downgrade idna to < 3.0 This is needed, since the requests library does not yet support `idna > 2.x`. See this for information: https://github.com/psf/requests/issues/5710 This... — committed to oleorhagen/integration by deleted user 3 years ago
- fix: pin idna<3 version becasue of version conflict between urlextract & requests can be resolved after https://github.com/psf/requests/issues/5710 is fixed — committed to karlicoss/promnesia by karlicoss 3 years ago
- fix: pin idna<3 version becasue of version conflict between urlextract & requests can be resolved after https://github.com/psf/requests/issues/5710 is fixed — committed to karlicoss/promnesia by karlicoss 3 years ago
@sethmlarson how long do we have to keep using older version of
idna? This is essentially blocking us from using latest version of it. I don’t think that should be suggested to anyone.@hartwork https://github.com/psf/requests/pull/5711 will fix this, @psf are just sitting on it until the next release
Upgrading idna requires dropping python 2.7 so whenever that happens unless someone adds python_version markers to the dependancies
@almssp @ViktorHaag The 2.x versions are still present and not yanked.
As
urllib3[secure]defineshttps://github.com/urllib3/urllib3/blob/3f21165969b838fda29898cbd7218ac9578e319b/setup.py#L119
This causes
pip20.2.1 to show warning: