Drop support for Django 1.2, Python 2.5.
Handle strings correctly.

Note that we did not use string_literals in the setup.py. That is
because Python 2 requires that the setup packages argument provide
a list of bytes, but Python 3 requires a list of strs. If
string_literals are used, you must mark the strings with ``b``
for it to work in Python 2, but that makes it fail in Python 3.
Add excludes to MANIFEST.in for py3 cache stuff.

Include one for compiled byte code as well.
Fix vertical spacing.
Move to explicit relative imports.
Move to format method for string formatting.
Revert "Fix meta-tests to use older methods."

This reverts commit b8f11ef4560695f1c269fab467c00bd84158ff91.

Python 2.5 and Django 1.2 support have been dropped, so we can use these
newer methods, and should, because the older ones have been deprecated
in the now-supported Python 3.
Drop * import in favor of explicit import of functions.
Add note regarding URLs defaults module deprecation.
Change to more idiomatic None comparison.
Standardize spacing and quotes in setup.py.
Set Django settings module absolutely, drop settings option.
Fix matrix exclusions in .travis.yml.

I think the way I formatted it in commit 741f09cd9ed will not
work, now that I watch Travis choke on it. :D
Use absolute import work around Django 1.3 bug.

The tests for Django 1.3 are failing using the relative import
(introduced in commit da53b574a4), because Django does this janky
thing where it django.core.management assumes your settings
are at the root of your project package, and imports that
package. Problem is, once a sub-package, such as gcframe.tests
is imported as a package (tests) Python will no longer let you
do a relative import beyond that new root. An absolute import
avoids that issue.
Test against latest security releases.
Handle a Django deprecation properly.

Should have done this in commit cb4eae7b7.
Bump minor version number.
Merge branch 'python3'