build(ci): Add Django@4 to tox

[DmytroLitvinov]

Closes #59

[peterbe]

You might need to drop 3.5. Right? Whatever Django 4 says :)

[peterbe]

Yeah, Django 4 is Python 3.8 and up

[DmytroLitvinov]

As for me opinion, I would do it as other packages in Django eco system do: they provide new release with support only for Django 2.2, 3.1, 3.2, 4.0 and Python 3.6^.

How do you see it, @peterbe ?

[peterbe]

As for me opinion, I would do it as other packages in Django eco system do: they provide new release with support only for Django 2.2, 3.1, 3.2, 4.0 and Python 3.6^.

I'm not entirely sure I understand you. But I'll phrase it myself and you can check if we are saying the same thing.

If someone needs to stick to Django 2, they can simply pin an old version of django-cache-memoize.
If we add support for Django 4.0 we'll just make a semver release and a big mention in the changelog that this project now only supports Python 3.8 and up.

[DmytroLitvinov]

And why we can't just add Django@4 in the tox.ini without dropping Django 2.2,3.1,3.2? We only need use Python 3.8^ for Django@4.0.

My proposal is to add Django@4.0 right now without any release or something. There is no code changes or something and even we follow semver, we can add new patch release where we point out that we added Django@4.0 to tox.ini for testing that package. (But again - without code changes in the library I would not do release). This is more for us right now to see that current version of package can be installed for Django@4.0

[peterbe]

Thanks!