#21628: Stop using the `imp` module
--------------------------------------+------------------------------------
Reporter: aaugustin | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Core (Other) | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by loic84):
As @aaugustin pointed in a github comment, these functions used to be
implemented as normal reentrant threads and that caused deadlocks
(#18251).
It seems the behavior of those functions changed in 3.3 as well, dunno if
the change affected us:
"Changed in version 3.3: The locking scheme has changed to per-module
locks for the most part. A global import lock is kept for some critical
tasks, such as initializing the per-module locks."
FWIW the python bug where the deprecation was discussed:
http://bugs.python.org/issue17177.
--
Ticket URL: <https://code.djangoproject.com/ticket/21628#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.4cbaa32093efc207b3d4b8f6ca6da162%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
