Merge ~cjwatson/lazr.restful:remove-relative-import-hack into lazr.restful:main

[Colin Watson]

Remove relative import hack from lazr.restful.frameworks.django

It's no longer needed on Python 3, since that always uses absolute imports.

[Jürgen Gmach (jugmac00)]

Looks good

Just curious - why do we not install Django for testing? Whenever Django decides to restructure its hiearachy / API, our tests will continue to pass, but the code will no longer work.

Who is using the Django integration?

review: Approve

[Colin Watson (cjwatson)]

SSO used it at one point (as indicated by https://bugs.launchpad.net/lazr.restful/+bug/640132), but no longer does. I'm afraid I have no idea who, if anyone, is using the Django integration at this point. This all long predates me, and since I don't really know its history or usage I've been hesitant to touch it more than necessary.

I've filed https://bugs.launchpad.net/lazr.restful/+bug/1956782 to consider removing this.

diff --git a/src/lazr/restful/frameworks/django.py b/src/lazr/restful/frameworks/django.py
index a7ae447..c3f9a85 100644
--- a/src/lazr/restful/frameworks/django.py
+++ b/src/lazr/restful/frameworks/django.py
@@ -20,14 +20,8 @@ from zope.schema import getFieldsInOrder
 from zope.traversing.browser.absoluteurl import AbsoluteURL
 
 import grokcore.component
-
-# Without this trickery, this module (called "django") will mask the
-# real Django modules. We could use "from __future__ import
-# absolute_import", but that would not work with Python 2.4.
-ObjectDoesNotExist = __import__(
-    "django.core.exceptions", {}
-).core.exceptions.ObjectDoesNotExist
-Manager = __import__("django.db.models.manager", {}).db.models.manager.Manager
+from django.core.exceptions import ObjectDoesNotExist
+from django.db.models.manager import Manager
 
 from lazr.restful import directives  # noqa: E402
 from lazr.restful.interfaces import (  # noqa: E402