Skip to content
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

Dependency conflict on macOS (arm) #756

Closed
fwornle opened this issue Jan 16, 2025 · 1 comment
Closed

Dependency conflict on macOS (arm) #756

fwornle opened this issue Jan 16, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@fwornle
Copy link

fwornle commented Jan 16, 2025

Bug

pip install docling
... throws the following error on macOS (arm):
ERROR: Cannot install docling==1.10.0, docling==1.11.0, docling==1.12.0, docling==1.12.1, docling==1.12.2, docling==1.13.0, docling==1.13.1, docling==1.14.0, docling==1.15.0, docling==1.16.0, docling==1.16.1, docling==1.17.0, docling==1.18.0, docling==1.19.0, docling==1.19.1, docling==1.2.0, docling==1.2.1, docling==1.20.0, docling==1.3.0, docling==1.4.0, docling==1.5.0, docling==1.6.0, docling==1.6.1, docling==1.6.2, docling==1.6.3, docling==1.8.5, docling==1.9.0, docling==2.0.0, docling==2.1.0, docling==2.2.0, docling==2.2.1 and docling==2.3.0 because these package versions have conflicting dependencies.

The conflict is caused by:
docling 2.3.0 depends on torch<3.0.0 and >=2.2.2; sys_platform != "darwin" or platform_machine != "x86_64"
docling 2.2.1 depends on torch<3.0.0 and >=2.2.2; sys_platform != "darwin" or platform_machine != "x86_64"
docling 2.2.0 depends on torch<3.0.0 and >=2.2.2; sys_platform != "darwin" or platform_machine != "x86_64"
docling 2.1.0 depends on torch<3.0.0 and >=2.2.2; sys_platform != "darwin" or platform_machine != "x86_64"
docling 2.0.0 depends on torch<3.0.0 and >=2.2.2; sys_platform != "darwin" or platform_machine != "x86_64"
docling 1.20.0 depends on deepsearch-glm<0.23.0 and >=0.22.0
docling 1.19.1 depends on deepsearch-glm<0.23.0 and >=0.22.0
docling 1.19.0 depends on deepsearch-glm<0.23.0 and >=0.22.0
docling 1.18.0 depends on deepsearch-glm<0.23.0 and >=0.22.0
docling 1.17.0 depends on deepsearch-glm<0.23.0 and >=0.22.0
docling 1.16.1 depends on deepsearch-glm<0.22.0 and >=0.21.1
docling 1.16.0 depends on deepsearch-glm<0.22.0 and >=0.21.1
docling 1.15.0 depends on deepsearch-glm<0.22.0 and >=0.21.1
docling 1.14.0 depends on deepsearch-glm<0.22.0 and >=0.21.1
docling 1.13.1 depends on deepsearch-glm<0.22.0 and >=0.21.1
docling 1.13.0 depends on deepsearch-glm<0.22.0 and >=0.21.1
docling 1.12.2 depends on deepsearch-glm<0.22.0 and >=0.21.0
docling 1.12.1 depends on deepsearch-glm<0.22.0 and >=0.21.0
docling 1.12.0 depends on deepsearch-glm<0.22.0 and >=0.21.0
docling 1.11.0 depends on deepsearch-glm<0.22.0 and >=0.21.0
docling 1.10.0 depends on deepsearch-glm<0.22.0 and >=0.21.0
docling 1.9.0 depends on deepsearch-glm<0.20.0 and >=0.19.1
docling 1.8.5 depends on deepsearch-glm<0.20.0 and >=0.19.1
docling 1.6.3 depends on docling-parse<0.3.0 and >=0.2.0
docling 1.6.2 depends on docling-parse<0.3.0 and >=0.2.0
docling 1.6.1 depends on docling-parse<0.3.0 and >=0.2.0
docling 1.6.0 depends on docling-parse<0.3.0 and >=0.2.0
docling 1.5.0 depends on docling-parse<0.3.0 and >=0.2.0
docling 1.4.0 depends on docling-parse<0.3.0 and >=0.2.0
docling 1.3.0 depends on docling-parse<0.0.2 and >=0.0.1
docling 1.2.1 depends on docling-parse<0.0.2 and >=0.0.1
docling 1.2.0 depends on docling-parse<0.0.2 and >=0.0.1

Using Python 3.13.1 and a fresh virtual environment (venv). I suspect, this conflict is not the intended behavior. Could you please check, if those dependency ranges can be extended/relaxed? Thank you

Steps to reproduce

  1. create a new virtual environment to have a clean python installation (3.13.1): python3 -m vent pdf
  2. activate the environment: source pdf/bin/activate
  3. install docking: pip install docling

Docling version

n/a - trying to install "the latest" version available via pip

Python version

3.13.1 (freshly installed)

@fwornle fwornle added the bug Something isn't working label Jan 16, 2025
@dolfim-ibm
Copy link
Contributor

Unfortunately python 3.13 only works with nightly builds of pytorch. We are waiting for the new torch release which will enable support. You can read more at #136

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants