opentelemetry-instrumentation-asyncclick still pins wrapt ~= 1.0
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 86/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- python
- Domain
- build-system
Research direction
Open instrumentation/opentelemetry-instrumentation-asyncclick/pyproject.toml and inspect its wrapt dependency constraint, comparing it with the click instrumentation mentioned in the issue. Reproduce the conflict with the provided uv pip compile command. Done means the contrib instrumentation requirements resolve alongside wrapt>=2 while asyncclick permits the expected wrapt range.
Written by the indexing model from the issue text.
Description
Describe your environment
OS: Ubuntu
Python version: Python 3.13
Package version: opentelemetry-instrumentation-asyncclick 0.66b0 (same on main), opentelemetry-contrib-instrumentations 0.66b0
What happened?
opentelemetry-instrumentation-asyncclick declares wrapt ~= 1.0:
https://github.com/open-telemetry/opentelemetry-python-contrib/blob/main/instrumentation/opentelemetry-instrumentation-asyncclick/pyproject.toml#L31
#4203 moved opentelemetry-instrumentation, click and 21 other instrumentations to support wrapt 2.x, but asyncclick was not part of it, probably because its constraint was written as ~= 1.0 rather than >=1.0.0, <2.0.0. As a result, installing opentelemetry-contrib-instrumentations forces wrapt down to 1.17.3 even when asyncclick is not used.
Steps to Reproduce
-
Create
requirements.in:opentelemetry-contrib-instrumentations==0.66b0 wrapt>=2 -
Resolve it:
uv pip compile requirements.in
Or in one command:
printf 'opentelemetry-contrib-instrumentations==0.66b0\nwrapt>=2\n' | uv pip compile -
Expected Result
The requirements resolve; asyncclick accepts wrapt >= 1.0.0, < 3.0.0, like the click instrumentation.
Actual Result
× No solution found when resolving dependencies:
╰─▶ Because opentelemetry-instrumentation-asyncclick==0.66b0 depends on
wrapt>=1.0,<2.dev0 and opentelemetry-contrib-instrumentations==0.66b0
depends on opentelemetry-instrumentation-asyncclick==0.66b0, we can
conclude that opentelemetry-contrib-instrumentations==0.66b0 depends on
wrapt>=1.0,<2.dev0.
And because you require opentelemetry-contrib-instrumentations==0.66b0
and wrapt>=2, we can conclude that your requirements are unsatisfiable.
Additional context
The click instrumentation already uses wrapt >= 1.0.0, < 3.0.0 after #4203
Would you like to implement a fix?
No
Tip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 1.1k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 21
Getting set up
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.
More from open-telemetry/opentelemetry-python-contrib
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
open-telemetry/opentelemetry-python-contrib#5118 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
open-telemetry/opentelemetry-python-contrib#5113 · 2 comments · 2 reactions ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
open-telemetry/opentelemetry-python-contrib#5100 ·
Maintainers usually reply within 1 day
-
feature-request
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
open-telemetry/opentelemetry-python-contrib#5071 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
open-telemetry/opentelemetry-python-contrib#5069 ·
Maintainers usually reply within 1 day
All issues in open-telemetry/opentelemetry-python-contrib
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
instance instance add
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
searxng/searx-instances#941 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
FluidNumerics/fluid-walk-blocker#89 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day