Comment 2 for bug 663155

Thanks Gary. I've linked a branch, and verified that locally I don't need to manually patch the settings module with this change for testing.

Regarding (a), the comment in the code there says more than I know:

# 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.

So if Python 2.4 is no longer supported (?) we could switch to absolute_import? Or perhaps you know a better way?

Cheers,
Michael