patch_span.py shouldn't format the traceback about signalfx-python-tracing HOT 2 CLOSED

Maybe I don't understand the purpose of patching the Span._on_error but all I know is a library I was using depends on this signalfx-python-tracing and it was messing up the error capture in jaeger.

from signalfx-python-tracing.

Thanks for reporting this @calbot. Unfortunately, this library only support Splunk APM as a backend/export destination even though it does speak the Jaeger protocol. This works as expected by Splunk APM so I don't think we make changes here to accommodate other backends like Jaeger.

Besides this library has been deprecated and is in maintenance mode. We recommend all customers to switch to splunk-otel-python or opentelemetry-python. I'd be more than happy to help you out with any issues over at https://github.com/open-telemetry/opentelemetry-python
Even if we did want to make this

from signalfx-python-tracing.