As far back as Django 1.4 (didn't check earlier), we use both these
patterns in the code:
import threading
try:
import threading
except ImportError:
import dummy_threading as threading
We also have logic in tests to skip if threading isn't available, however,
I can't believe that Django is usable without threading given we use the
first style of import (without a fallback) in many places
(db.models.loading, db.utils, test.testcases, + more).
Docs say:
"The dummy_threading
<https://docs.python.org/2/library/dummy_threading.html#module-dummy_threading>
module is provided for situations where threading
<https://docs.python.org/2/library/threading.html#module-threading> cannot
be used because thread
<https://docs.python.org/2/library/thread.html#module-thread> is missing."
https://docs.python.org/2/library/threading.html
"The [thread] module is optional. It is supported on Windows, Linux, SGI
IRIX, Solaris 2.x, as well as on systems that have a POSIX thread (a.k.a.
“pthread”) implementation."
https://docs.python.org/2/library/thread.html#module-thread
This doesn't answer the question of what systems it *is* needed on. Unless
there's an objection, I think we can remove dummy_threading fallbacks?
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/08135f96-7429-4641-8a82-0cd47395ac09%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
