Poetry unable to resolve urllib3 dependency while pip is able to

[MeSmileyFace]

Describe the bug

I'm getting dependency conflict when trying to lock dependencies with poetry. It states that botocore 1.35.87 depends on urllib3(>=1.25.4, <1.27) therefore its unable to resolve it due to one of my custom packages requiring urllib3(2.3.0).

In the screenshot above, we can see that there are two urllib3 constraints where the first one(underlined with red) seems to contradict the second one(underlined with yellow)?

It may be important to note that it resolves the dependencies successfully when installing the requirements with pip install -r requirements.txt but the problem lies when using poetry lock.

Regression Issue

• Select this option if this issue appears to be a regression.

Expected Behavior

To have the dependencies resolved

Current Behavior

Because botocore (1.35.87) depends on urllib3 (>=1.25.4,<1.27)
and my-package depends on urllib3 (2.3.0), botocore is forbidden.
So, because my-package depends on botocore (1.35.87), version solving failed.

Reproduction Steps

Have a package requiring urllib3 version 2.3.0 and botocore 1.35.87 and try poetry lock

Possible Solution

Perhaps remove the constraint limiting urllib3 to <1.27?

Additional Information/Context

No response

SDK version used

Python 3.10.15

Environment details (OS name and version, etc.)

Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye

[nateprewitt]

Hi @MeSmileyFace, you may need to ensure that you're locking with the same (or lowest) Python version you're intending to deploy with.

The constraints you highlight state in plain terms:

• The red line declares we only support urllib3 1.x being installed on Python 3.9 and earlier.
• The yellow line declares we support urllib3 2.x, except 2.2.0, for Python 3.10 and later.

If you're trying to force use of urllib3 2.x before Python 3.10, we don't support that. We cannot safely add support for all systems prior to changes made in Python 3.10 with PEP 644.

If you are using 3.10 and it's not resolving, that sounds like a potential issue with Poetry. You may consider reaching out to their issue tracker if you're seeing it cannot resolve markers correctly. Those have been supported by pip since ~2015.

[MeSmileyFace]

Hi @nateprewitt in my desperation with the dependency conflict and exhaustion of many other solutions I have completely overlooked the fact that one shows >= 3.10 and the other < 3.10. Seems like i had simply chosen to believe that this was the issue since it seemed like the easiest fix, I'm sorry to have wasted your time and thank you for the swift response.

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.