#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 merb): @aaugustin i think we could just ignore this issue. Currently I tried: https://code.djangoproject.com/attachment/ticket/18251/threading_lock.tar.gz On Python 2.7.5+ and on Python 3.3.2+ the issue never occured. Without calling {{{imp.acquire_lock()}}} or {{{imp.release_lock()}}} Maybe the "test" itself is somehow not correct anymore. But I think its due to the fact that we now (since the last commit https://github.com/django/django/compare/fe1389e911b0...4a56a93cc458) use https://pypi.python.org/pypi/importlib a backport of importlib for python 2.7 due to the fact that the next django version won't be compatible to python 2.6. So just remove imp and we are fine. -- Ticket URL: <https://code.djangoproject.com/ticket/21628#comment:3> 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.787265447b2a81bc3ffd027a194c6e65%40djangoproject.com. For more options, visit https://groups.google.com/groups/opt_out.