Need for a lock when setting the global `Tracer`

Hey @mikebryant

Currently we have a lock used when setting opentracing.Tracer (and also, indirectly, when creating a Tracer through the OPENTRACING_TRACER_CALLABLE value), and I’m wondering whether this is needed.

Before Django 1.10, the middleware is supposed to be initialized only once when the first request takes place (https://docs.djangoproject.com/en/1.9/topics/http/middleware/#init)

As of Django 1.10, the middleware will be initialized only once at server start (https://docs.djangoproject.com/en/1.10/topics/http/middleware/#init-get-response)

Is there any advanced need to take a lock? I remember you mentioning forking, but I have forgotten the details now 😉

[carlosalberto]

Thanks Mike!

[carlosalberto]

Closing as this has been solved for long time 😉