Determine this is the right repository
Summary of the issue
Expand upon the logic in the Feature Gating LLD (internal doc) and the current resolve_feature_flags() implementation to better handle nuances between how opentelemetry (OTEL) handles the value None and how Python handles the value None.
Namely, OTEL tends to use None in functions such as get_tracer() to mean: use the default provider, whereas to a Pythonista we might interpret None to mean don't use a provider, don't do anything, leave tracing disabled.
This conflict should be resolved in the LLD and a future PR.
API client name and version
No response
Reproduction steps: code
Reproduction steps: supporting files
Reproduction steps: actual results
Reproduction steps: expected results
No response
OS & version + platform
No response
Python environment
No response
Python dependencies
No response
Additional context
No response
Determine this is the right repository
Summary of the issue
Expand upon the logic in the Feature Gating LLD (internal doc) and the current
resolve_feature_flags()implementation to better handle nuances between how opentelemetry (OTEL) handles the valueNoneand how Python handles the valueNone.Namely, OTEL tends to use
Nonein functions such asget_tracer()to mean: use the default provider, whereas to a Pythonista we might interpretNoneto mean don't use a provider, don't do anything, leave tracing disabled.This conflict should be resolved in the LLD and a future PR.
API client name and version
No response
Reproduction steps: code
Reproduction steps: supporting files
Reproduction steps: actual results
Reproduction steps: expected results
No response
OS & version + platform
No response
Python environment
No response
Python dependencies
No response
Additional context
No response