psycopg2-binary dependency conflict

[RyanSiu1995]

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

[cdvv7788]

psycopg-binary is not recommended for production usage. It should not be used as a dependency in general. It is more of a workaround for local setups.

[owais]

Since this was closed, we've reworked how we handle instrumentation <> library dependencies and I think it should be possible to support both with the same instrumentation. Would be great if someone could experiment and figure out if it is doable easily.

[cdvv7788]

I can give it a try this weekend. However note that the package discourages the usage of psycopg-binary for anything that is not testing https://pypi.org/project/psycopg2-binary/

[owais]

Agree but if we can easily support both, we can make life easier for people using binary in dev/CI while still using opentelemetry.

[srikanthccv]

relevant discussion and some proposal here #610.