Remove Django 1.6 (and Python 2.6) Support

[carltongibson]

Django 1.6 is out of extended support — it is no longer receiving even security patches — it should not be used.

We should drop support too:

• Helps with the maintenance burden for DRF
• Doesn't give implicit blessing to keep using Django 1.6

Todo:

• Remove Django 1.6 and Python 2.6 from text matrix
• Remove 1.6 related code from compat.py
• Adjust README and Release Notes.

Once we get here (and 1.4 is EOL) we could/should adopt a policy of following Django's current "extended support" versions.

[carltongibson]

@tomchristie @xordoquy — Guys, if you can spare a moment, can I get a sanity check on ResolveModelWithPatchedDjangoTests please?

1. Here in setUp we monkey patch get_model. (OK)
2. In tearDown the comment says "Revert monkey patching" but assigns the stored reference to a different attribute path.

This looks like an error to me. Can you advise?

Thanks!

[carltongibson]

See 6e86a53 — I've corrected the logic, on the assumption it was an error.

[tomchristie]

Don't understand - all lines that reference it use rest_framework.utils.model_meta.models.get_model right?

[carltongibson]

No. There's an extra .models. in tearDown

Pre-change setUp:

 rest_framework.utils.model_meta.get_model

Pre-change tearDown:

 rest_framework.utils.model_meta.models.get_model

[carltongibson]

OK. This is ready to review.

Just an aside: serializers.py is pulling OrderedDict in from fields.py via the * import. Not really an issue but confused me for a bit.

[jpadilla]

This looks good to me. Thanks for putting this together @carltongibson!

[carltongibson]

@jpadilla No probs — just a bit of yak shaving from #3404. You should merge it whilst @tomchristie isn't looking 😈

[tomchristie]

😨

[tomchristie]

He's right, tho'

[xordoquy]

👀

[carltongibson]

Are we going to have this? (Can rebase if so)

[tomchristie]

Rebased. Superseeded by #3429.

[carltongibson]

Confused. This is #3429

[carltongibson]

Ah, now I see it...