open-telemetry / open-telemetry/opentelemetry-python-contrib
psycopg2-binary dependency conflict
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 1.1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 16
Description
Describe your environment
> pip freeze | grep psyco
opentelemetry-instrumentation-psycopg2==0.22b0
psycopg2==2.8.6
Steps to reproduce
Install psycopg2 instead of psycopg2-binary
What is the expected behavior?
No error message popping up
What is the actual behavior?
The instrumentation library will throw this error for every run.
DependencyConflict: requested: "psycopg2-binary >= 2.7.3.1" but found: "None"
Additional context
The instrumentation actually works as expected for psycopg2. So, the package instrumented should be both psycopg2-binary and psycopg
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 reproducing the installation with psycopg2 rather than psycopg2-binary, then locate the instrumentation dependency check that reports the missing package. Verify the change against the existing instrumentation behavior; done means psycopg2 runs without a DependencyConflict while psycopg2-binary remains supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100