[GH-ISSUE #673] [Deps] Python version and poetry.lock bumps required for poetry install in dev mode #136

New issue

Closed

opened 2026-03-02 15:56:06 +03:00 by kerem · 1 comment

kerem commented

2026-03-02 15:56:06 +03:00

Owner

Originally created by @goosethedev on GitHub (Aug 14, 2024).
Original GitHub issue: https://github.com/probberechts/soccerdata/issues/673

I forked and cloned the repo to contribute. When doing poetry install it gives the error:

Installing dependencies from lock file
pyproject.toml changed significantly since poetry.lock was last generated. Run `poetry lock [--no-update]` to fix the lock file.

When doing poetry lock --no-update it becomes:

The current project's supported Python range (>=3.9,<3.13) is not compatible with some of the required packages Python requirement:
  - sphinx requires Python >=3.10, so it will not be satisfied for Python >=3.9,<3.10
  - sphinx requires Python >=3.10, so it will not be satisfied for Python >=3.9,<3.10
  - sphinx requires Python >=3.10, so it will not be satisfied for Python >=3.9,<3.10

Because no versions of sphinx match >8.0.0,<8.0.1 || >8.0.1,<8.0.2 || >8.0.2,<9.0.0
 and sphinx (8.0.0) requires Python >=3.10, sphinx is forbidden.
And because sphinx (8.0.1) requires Python >=3.10, sphinx is forbidden.
So, because sphinx (8.0.2) requires Python >=3.10
 and soccerdata depends on Sphinx (^8.0.0), version solving failed.

  • Check your dependencies Python requirement: The Python requirement can be specified via the `python` or `markers` properties
    
    For sphinx, a possible solution would be to set the `python` property to ">=3.10,<3.13"
    For sphinx, a possible solution would be to set the `python` property to ">=3.10,<3.13"
    For sphinx, a possible solution would be to set the `python` property to ">=3.10,<3.13"

Bumping python in pyproject.toml solves the issue:

[tool.poetry.dependencies]
python = ">=3.10,<3.13"

OS: Pop_OS! (Ubuntu) 22.04
Python ver. 3.12.4
Poetry ver. 1.8.3

Originally created by @goosethedev on GitHub (Aug 14, 2024). Original GitHub issue: https://github.com/probberechts/soccerdata/issues/673 I forked and cloned the repo to contribute. When doing `poetry install` it gives the error: ``` Installing dependencies from lock file pyproject.toml changed significantly since poetry.lock was last generated. Run `poetry lock [--no-update]` to fix the lock file. ``` When doing `poetry lock --no-update` it becomes: ``` The current project's supported Python range (>=3.9,<3.13) is not compatible with some of the required packages Python requirement: - sphinx requires Python >=3.10, so it will not be satisfied for Python >=3.9,<3.10 - sphinx requires Python >=3.10, so it will not be satisfied for Python >=3.9,<3.10 - sphinx requires Python >=3.10, so it will not be satisfied for Python >=3.9,<3.10 Because no versions of sphinx match >8.0.0,<8.0.1 || >8.0.1,<8.0.2 || >8.0.2,<9.0.0 and sphinx (8.0.0) requires Python >=3.10, sphinx is forbidden. And because sphinx (8.0.1) requires Python >=3.10, sphinx is forbidden. So, because sphinx (8.0.2) requires Python >=3.10 and soccerdata depends on Sphinx (^8.0.0), version solving failed. • Check your dependencies Python requirement: The Python requirement can be specified via the `python` or `markers` properties For sphinx, a possible solution would be to set the `python` property to ">=3.10,<3.13" For sphinx, a possible solution would be to set the `python` property to ">=3.10,<3.13" For sphinx, a possible solution would be to set the `python` property to ">=3.10,<3.13" ``` Bumping `python` in `pyproject.toml` solves the issue: ``` [tool.poetry.dependencies] python = ">=3.10,<3.13" ``` OS: Pop_OS! (Ubuntu) 22.04 Python ver. `3.12.4` Poetry ver. `1.8.3`

kerem

2026-03-02 15:56:06 +03:00

closed this issue
added the
dependencies
label

kerem commented

2026-03-02 15:56:07 +03:00

Author

Owner

@probberechts commented on GitHub (Aug 15, 2024):

Thanks. It seems we were not ready yet for Sphinx v8. It also gave problems on readthedocs. I've reverted the Sphinx version bump in ca93d87 and this should fix the dependency resolution problem.

@probberechts commented on GitHub (Aug 15, 2024): Thanks. It seems we were not ready yet for Sphinx v8. It also gave problems on readthedocs. I've reverted the Sphinx version bump in ca93d87 and this should fix the dependency resolution problem.

kerem referenced this issue

2026-03-02 15:57:21 +03:00

[PR #136] [MERGED] Update dependency Sphinx to v6 #310