-
Notifications
You must be signed in to change notification settings - Fork 536
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add dependency information in setup.py for instrumentation #749
Comments
It would be ideal if an instrumentation package could provide hints about which other packages it is compatible with without forcing users to install those packages. Unfortunately, the Python packaging ecosystem does not allow that and the only thing it allows is to specify another package as a dependency. This makes things tricky for instrumentation pacakges. We delibrately made the decision to not specify instrumented libs/frameworks as dependencies in order to allow a lot more flexibility into how instrumentation is installed, bundled and used on a wide variety of environments. More details here: open-telemetry/opentelemetry-python#1729 That said, all instrumentation packages do specify all the packages they instrument as optional dependencies under For example, the following raises errors at install time
But this works:
|
The |
Before opening a feature request against this repo, consider whether the feature should/could be implemented in the other OpenTelemetry client libraries. If so, please open an issue on opentelemetry-specification first.
Is your feature request related to a problem?
If so, provide a concise description of the problem.
httpx >= 0.18.0, < 0.19.0
. Instrumentation won't function if dependencies requirements not meet.opentelemetry-python-contrib/instrumentation/opentelemetry-instrumentation-httpx/src/opentelemetry/instrumentation/httpx/package.py
Line 16 in 4e3aaa5
Describe the solution you'd like
What do you want to happen instead? What is the expected behavior?
Add version requirement info in setup.py, so the dependency requirements/conflicts can be solved automatically.
Describe alternatives you've considered
Which alternative solutions or features have you considered?
Additional context
Add any other context about the feature request here.
The text was updated successfully, but these errors were encountered: