🔥 Drop Python 3.3 Support

[jefftriplett]

Since Python 3.3 is no longer maintained and it's usage is next to nothing, we might as well speed up our test suite by dropping support for it. See notes here for how small it's usage was a year+ ago: pypa/pip#3796

[fcurella]

should we also drop django <1.8?

[coveralls]

Coverage remained the same at 97.112% when pulling 7659414 on drop-python-3-3 into c3117b2 on master.

[jefftriplett]

@fcurella there's a good argument to be made for it. I'm not really sure what our user base is. I felt good about dropping Python 3 since python.org stopped supporting it.

The release chart with the dates of the old versions kind of puts it into perspective: https://www.djangoproject.com/download/#supported-versions

I don't think it hurts to support some older versions but I'm not sure where that line is. Do you or
@frankwiles have strong feelings about it?

[fcurella]

I'd say let's support one LTS before the currently supported one (which currently 'resolves' to 1.8+). That should give enough time to upgrade even for the most conservative of our users.

And when django 2.2 will be out, we can drop < 1.11

[goodtune]

I'd go so far as to drop the non-LTS versions that have gone out of support (1.9 already, 1.10 at years end) on the basis that older releases of django-test-plus will still be available to support older projects.

I wouldn't go hard at making breaking changes, just stop certifying against unsupported versions of Django as early as possible.

[jefftriplett]

I'm personally +1 for making a new PR to just target Django versions to keep this relatively focused scope.

I'm +1 for supporting both LTSs when it makes sense. I'm +0 supporting 1.9 and 1.10 if we get those for free already and a lot of people are still on them.

[frankwiles]

Yeah let's definitely drop <1.8 as it really shouldn't matter much.

I think we should continue to test 1.8+ until we run into a situation where we cannot support 1.9 or 1.10. This way we'll see if/when it breaks and can make a note in the docs about "If you need Django 1.9.x you have to use before dtp version <= x.y.z". But we'll ditch support for anything not supported upstream at the first issue and not work around it.

Make sense?

[jefftriplett]

Please refer to #62 for that followup.

[goodtune]

All good with @frankwiles approach.