Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
internal library dosen't get version from git repo
See original GitHub issue-
I am on the latest Poetry version.
-
I have searched the issues of this repo and believe that this is not a duplicate.
-
If an exception occurs when executing a command, I executed it again in debug mode (
-vvvoption). -
OS version and name: MacOS 11.1 (20C69)
-
Poetry version:
1.1.13(tried also on1.2.0b1) -
- Link of a Gist with the contents of your pyproject.toml file: in the issues
Issue
I have a repo A that is using 2 other repos B and C
C is also using B
A’s pyproject.toml
B = {git = "<B's github repo>", branch = "my-branch"}
C = {version="^0.5.8"}
B’s pyproject.toml (in my-branch branch)
[tool.poetry]
name = "B"
version = "0.31.0"
C’s pyproject.toml
B = {version=">=0.30"}
The current versions of B in my PyPI server are (0.30.0 || 0.30.1 || 0.30.2 || 0.30.3 || 0.30.4)
It seems that when locking C inside A, C’s not aware B’s version is acceptable
Because no versions of B match >0.30,<0.30.1 || >0.30.1,<0.30.2 || >0.30.2,<0.30.3 || >0.30.3,<0.30.4 || >0.30.4
and B (0.30.0) depends on B (0.30.0), B (>=0.30,<0.30.1 || >0.30.1,<0.30.2 || >0.30.2,<0.30.3 || >0.30.3,<0.30.4 || >0.30.4) requires B (0.30.0).
And because B (0.30.1) depends on B (0.30.1)
and B (0.30.2) depends on B (0.30.2), B (>=0.30,<0.30.3 || >0.30.3,<0.30.4 || >0.30.4) requires B (0.30.0 || 0.30.1 || 0.30.2).
And because B (0.30.3) depends on B (0.30.3)
and B (0.30.4) depends on B (0.30.4), B (>=0.30) requires B (0.30.0 || 0.30.1 || 0.30.2 || 0.30.3 || 0.30.4).
Because no versions of C match >0.5.8
and C (0.5.8) depends on B (>=0.30), C (>=0.5.8) requires B (>=0.30).
Thus, C (>=0.5.8) requires B (0.30.0 || 0.30.1 || 0.30.2 || 0.30.3 || 0.30.4).
And because B (rev my-branch) depends on B (rev my-branch), C (>=0.5.8) is incompatible with B (rev my-branch).
So, because A depends on both B (branch my-branch) and C (>=0.5.8), version solving failed.
I tried to publish my-branch as a beta branch, changed A’s to use this version, and still had the same issue
Issue Analytics
- State:
- Created a year ago
- Reactions:4
- Comments:17 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I removed the problematic sckitlearn package and now the solving is finishes successfully 100% of the time the issue now is that it can’t get a valid version of
uvicorn(albus is from my private repo)but reading the
-vvvlogs I do see that it found a valid versionright after locking the file, I see those logs (and those are the only libs with extras)
Albus’s pyproject
pyproject of the repo I’m trying to update
full logs are attached poetry.log
@dimbleby still no repo but a major update