Transitive dependency causes Dependency walk failed at

[absalukaskosina]

We have a common library with following setup (shorten and redacted):
pyproject.toml

[tool.poetry]
name = "commons"
version = "1.2.25"
readme = "README.md"
packages = [{ include = "commons", from = "src" }]

[[tool.poetry.source]]
name = "PyPI"
priority = "primary"

[[tool.poetry.source]]
name = "jfrog"
url = "company_frog"
priority = "supplemental"


[tool.poetry.dependencies]
python = "~3.10"
numpy = [
   {version = ">=2.1.2", markers = "sys_platform != 'darwin'"},
   {version = "<2.0.0", markers = "sys_platform == 'darwin'"}
]

The reason for this is that one of our services uses Ultralytics with following PR , so in order to make it work, we had to limit Numpy for MacOS.

And second project use as dependency with following setup:

[tool.poetry]
name = "service-project"
version = "1.2.0"
readme = "README.md"

[[tool.poetry.packages]]
include = "service"
from = "src"

[[tool.poetry.source]]
name = "PyPI"
priority = "primary"

[[tool.poetry.source]]
name = "jfrog"
url = "company_frog"
priority = "supplemental"

[tool.poetry.dependencies]
python = "~3.10"
commons = "^1.2.25"

Generally poetry install works and we have no problem in development and testing.

The problem starts when we try to export requirements for docker image using

poetry export --without-hashes --format=requirements.txt --without dev,research --with-credentials > requirements.txt

Which will cause

  Stack trace:
   1  ~/.local/pipx/venvs/poetry/lib/python3.10/site-packages/poetry_plugin_export/walker.py:125 in get_project_dependencies
       123│         )
       124│
     → 125│     nested_dependencies = walk_dependencies(
       126│         dependencies=project_requires,
       127│         packages_by_name=packages_by_name,

  RuntimeError
  Dependency walk failed at numpy (>=1.21.4)

Is there any way how it is possible to make export plugin work with following setup?

[zoonman]

I have a similar issue with dependencies.

DependencyWalkerError
  The `torch` package has the following compatible candidates `[Package('torch', '2.2.2')]`;  but, the exporter dependency walker previously elected `torch (2.6.0+cpu)` which is not compatible with the dependency `torch (>=2.2.0,<2.3.0)`.

I have to define torch like

[tool.poetry.dependencies]

torch = [
    { version = "2.6.0+cpu", platform = "linux", source = "pytorch" },
    { version = "2.6.0+cpu", platform = "win32", source = "pytorch" },
    { version = "^2.2.0", platform = "darwin", markers="platform_machine == 'x86_64'", source = "pypi" },
    { version = "2.6.0", platform = "darwin", markers="platform_machine == 'arm64'", source = "pypi" }
]

I run export on Windows, why does it even try to resolve darwin markers?