python-poetry / python-poetry/poetry
git versioning tags not explained
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 34.3k
- Forks
- 2.5k
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 30
Description
- I have searched the issues of this repo and believe that this is not a duplicate.
Issue
Can somebody explain the difference between:
uberdbutils (0.0.22 git branch master)
and
uberdbutils (0.0.22 git rev master)
Especially as it produces a conflict that makes it impossible to upgrade a package:
Because uber-schema (2.1.1) depends on uberdbutils (0.0.22 git rev master)
and no versions of uber-schema match >2.1.1,<3.0.0, uber-schema (>=2.1.1,<3.0.0) requires uberdbutils (0.0.22 git rev master).
So, because grants-pipeline depends on both uberdbutils (0.0.22 git branch master) and uber-schema (^2.1.1), version solving failed.
The package blocks for uberdbutils btw in poetry.lock in grants-pipeline & uber-schema are exactly the same.
So this is driving my crazy, uberdbutils is referenced by uber-schema & grants-pipeline in pyproject.toml & poetry.lock exactly the same, but poetry calls it 0.0.22 git rev master here and 0.0.22 git branch master there???
(And no, there have been no commits to uberdbutils has not been updated in 18 months.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the uberdbutils entries in the referenced pyproject.toml and poetry.lock files, then trace how Poetry represents git branch and revision constraints. Determine what distinguishes the two labels and document the explanation, including why the resolver treats them as conflicting. No documentation file or test is identified in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, python
- Domain
- build-system, tooling
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100