Poetry python version resolution behavior question

[RavindhranSankar]

Project setup:

Main_module

• should support python 37 - 311 (including 311)
• main_module imports lib_module as one of its dependencies

[tool.poetry.dependencies]
python = ">=3.7,<3.12"
lib-module = ">=1.0.0"

lib_module:
ver 1.x: support python37-310

[tool.poetry.dependencies]
python = ">=3.7, <3.11"

ver 2.x supports python 310-311

[tool.poetry.dependencies]
python = ">=3.11, <3.12"

---

Expected behavior:
Running poetry update on main module should recognize that python version >=3.7,<3.12 can be supported by using the different lib module versions.

---

Actual behavior:
Poetry will complain that neither lib_module version (1.x, 2.x) singularly completely supports the python version range >=3.7,<3.12.

[dimbleby]

correct. split the dependency manually:

lib-module = [
  { version = "<2", python = "<3.11" },
  { version = ">=2", python = ">=3.11" },
]

[RavindhranSankar]

Thanks for the response. I got my system to work !

---

I had tried the split dependency approach earlier, and ran into an error that I couldn't understand. Maybe there is something about this error message that can be improved.

I would do the following:

lib-module = [
  { version = "1.2.6", python = "<3.11" },
  { version = "2.1.5", python = ">=3.11" },
]

However, when I would try to poetry update on a python 3.7(say), the error message would complain that lib_module-2.1.5 was not compatible with py37. Which was very confusing as it should not have been trying to use 2.1.5 and should be using 1.2.6 instead. Attached screenshot of the error message

This gave the impression that split dependency is not working as I would have expected.

---

Real Issue:

Through a process of elimination, I was able to find the real issue in my pyproject.toml.
It was not the split dependency behavior, but the inclusion of a different package:

[tool.poetry.dev-dependencies]
pytest-asyncio = ">=0.21.2"

That seemed to break the dependency resolution..