- OS version and name: OS X 10.14.5
- Poetry version: 0.12.17
[tool.black]
skip-string-normalization = true
[tool.poetry]
name = "kompost"
version = "0.1.0"
description = ""
authors = ["Software Team <software@software.com>"]
[tool.poetry.dependencies]
celery = "*"
flask-celeryext = "*"
[build-system]
requires = ["poetry"]
build-backend = "poetry.masonry.api"
Issue
poetry install --dry-run 5.7s Fri 19 Jul 14:57:40 2019
Updating dependencies
Resolving dependencies... (24.2s)
[RecursionError]
maximum recursion depth exceeded
install [--no-dev] [--dry-run] [-E|--extras EXTRAS] [--develop DEVELOP]
poetry debug:resolve -vvv
Resolving dependencies...
1: fact: kompost is 0.1.0
1: derived: kompost
1: fact: kompost depends on celery (*)
1: fact: kompost depends on flask-celeryext (*)
1: selecting kompost (0.1.0)
1: derived: flask-celeryext (*)
1: derived: celery (*)
PyPI: 7 packages found for flask-celeryext *
PyPI: 132 packages found for celery *
0: Duplicate dependencies for celery
0: Different requirements found for celery (>=3.1) and celery (>=4.3).
1: Version solving took 0.096 seconds.
1: Tried 1 solutions.
0: Retrying dependency resolution for Python (>=3.7,<3.8).
1: fact: kompost is 0.1.0
1: derived: kompost
1: fact: kompost depends on celery (*)
1: fact: kompost depends on flask-celeryext (*)
1: selecting kompost (0.1.0)
1: derived: flask-celeryext (*)
1: derived: celery (*)
0: Duplicate dependencies for celery
0: Different requirements found for celery (>=3.1) and celery (>=4.3).
I think this problem is too impactful to be quiet for so long(while work arounds might be useful, they don’t solve the issue) The reason why I tried poetry was because of its dependency resolution(in particular it’s support for multiple OS’es resolution). I know this is open source and don’t take this as a demand for a quick fix or anything like that, but could we have some kind of update on the issue? Is this something that someone with minimal knowledge of the dependency resolution algorithm could help out?
I second this issue. It makes it impassible to select different versions depending on operating system. This is critical for packages where specially compiled versions are needed on windows… because of windows.
Got this error while running
poetry installon GitHub runners for all systems: ubuntu-latest, windows-latest, macos-latest.The error was same:
Everything resolves without problem on desktop machine. I removed
poetry.lockfile and entire virtual environment and reinstalled it all from scratch, then pushed to the runners and got the same error.The project is open source, so GitHub Actions build is open and visible along with the corresponding commit: https://github.com/vduseev/opensearch-logger/runs/4138254625?check_suite_focus=true.
The dependencies looked like this.
Full traceback is attached: traceback.txt.
I can confirm that this issue is resolved in the prerelease
1.1.0a3@rayluo The 1.1.0 stable release should be available in August.
I second what @vduseev is saying. On GH Actions (ubuntu-latest), we faced this issue even with a very simple dependencies file using poetry@1.1.11:
Downgrading to 1.1.10 fixed the issue for us (with no other changes). You can find the failed run (1.1.11), the successful run (1.1.10) and the commit that fixed it behind these links.
I’m encountering the same issue. What I did is this (starting from a clean project):
I’m running Python 3.7.2 on Windows 10. Does anybody know a work around until this is fixed?
I have a poetry project on Linux machine which builds without issues. Today I have cloned this project to Mac machine, removed
poetry.lockand this issue occurred. poetry version 1.1.4 Here is the-vvverror log.Same issue when I run
poetry add scrapy.looks like this was duplicated at #3626 and #3749, both of which went on to agree that it was a problem caused by the now deprecated
get-poetry.pyinstallerOur problem reported in one of the comments in this issue is fixed in the
1.1.0aseries releaseHi @philipbel! unfortunately, the only workaround for me was editing ‘spyder-kernels’ - here my fork updated to spyder-kernels 1.9 https://github.com/danieltomasz/spyder-kernels, you could fork it for yourself, I declared it as an github dependency in my pyproject.toml
spyder-kernels = { git = "https://github.com/danieltomasz/spyder-kernels.git", branch = "poetry" }I am waiting for poetry team to solve that, spyder team doesn’t want to remove this double declaration in their code,
Removing the
poetry.lockfile does the trick,poetry addworks again. It’s slow, but it works.