Resolving dependencies bug
See original GitHub issueHi
I have a package with next pyproject.toml:
[tool.poetry]
name = "dphelper"
version = "0.0.94.dev0"
description = ""
authors = ["Alex Tonkonozhenko <...>"]
[tool.poetry.dependencies]
python = "*"
psycopg2 = "^2.7"
xxxxxxxxxx = "^0.0"
s3transfer = "^0.1"
pyhocon = "^0.3"
boto3 = "^1.7"
pybars3 = "^0.9"
yyyyyyyyy = "^0.7"
troposphere = "^2.2"
retrying = "^1.3"
mock = "^2.0"
functools32 = {version = "^3.2", python = "~2.7"}
futures = {version = "^3.1", python = "~2.7"}
[tool.poetry.dev-dependencies]
regex = "^2018.2"
simplejson = "^3.15"
pyspark = "^2.3"
requests_mock = "^1.5"
Werkzeug = "^0.14"
findspark = "^1.2"
slacker = "^0.9"
tqdm = "^4.23"
pandas = "^0.22"
elasticsearch = "^5.5"
ipython = "^5.7"
requests = "^2.18"
ipywidgets = "^7.2"
[[tool.poetry.source]]
name = "...."
url = "https://....../pypi/packages"
When I’m trying to add it to another poetry project I get next error:
(.venv) ➜ hello poetry add ......
Using version ^0.0.93 for ......
Updating dependencies
Resolving dependencies... (0.4s)
Package operations: 1 install, 0 updates, 0 removals
Writing lock file
- Installing pyyaml (3.12.win32-py3.5)
[VenvCommandError]
Command ['pip', 'install', '--no-deps', '-r', '/var/folders/rs/xqvskktn065cs4_s00s919lm0000gn/T/pyyaml-3.12.win32-py3.5llvpkpreqs.txt'] errored with the following output:
Collecting pyyaml==3.12.win32-py3.5 (from -r /var/folders/rs/xqvskktn065cs4_s00s919lm0000gn/T/pyyaml-3.12.win32-py3.5llvpkpreqs.txt (line 1))
Could not find a version that satisfies the requirement pyyaml==3.12.win32-py3.5 (from -r /var/folders/rs/xqvskktn065cs4_s00s919lm0000gn/T/pyyaml-3.12.win32-py3.5llvpkpreqs.txt (line 1)) (from
versions: 3.10, 3.11, 3.12)
No matching distribution found for pyyaml==3.12.win32-py3.5 (from -r /var/folders/rs/xqvskktn065cs4_s00s919lm0000gn/T/pyyaml-3.12.win32-py3.5llvpkpreqs.txt (line 1))
You are using pip version 9.0.1, however version 10.0.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
[BUG] npm ci can't resolve dependencies without --force, or ...
An easy way to do this is to run, for example, npm config set legacy-peer-deps=true --location=project and commit the .npmrc file to your...
Read more >Unable to resolve dependency tree error when installing npm ...
You have dependency conflict (incorrect and potentially broken dependency) as it says, so try to run the command with --force , or --legacy-peer ......
Read more >Could not resolve dependencies - MuleSoft Help Center
Could not resolve dependencies. <p>I am trying to learn Mulesoft. I have no Java experience, so this might seem like a basic question/solution....
Read more >Customizing resolution of a dependency directly
Dependency resolve rules provide a very powerful way to control the dependency resolution process, and can be used to implement all sorts of...
Read more >NuGet Package Dependency Resolution - Microsoft Learn
Details on the process through which a NuGet package's dependencies are resolved and installed in both NuGet 2.x and NuGet 3.x+.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I just published a new bugfix release. It should fix this issue.
Sorry about that.
The issue looks fixed. Thanks!