Incompatibility with Django 3

First, thank you very much for this great plugin!

While testing the deployment of an app using django-private-storage in an environment with the recently release Django 3.0, I noticed that django-private-storage attempts to import django.utils.six in fields.py.

As Django 3.0 has removed private Python 2 compatibility APIs like django.utils.six, trying to import it raises a ModuleNotFoundError.

See https://docs.djangoproject.com/en/3.0/releases/3.0/#removed-private-python-2-compatibility-apis for details; the Django release notes suggest to either remove usage of this vendored library or switching to using six directly.

[wiegandm]

I have created two PRs (#42 and #45) which should address this issue – more specifically, a tox test matrix built on the changes in #43 also succeeds for Django 3.0.

Merging both #42 and #45 would make django-private-storage work with Django 3 (AFAICT, at least the unit tests succeed), but at the price of losing compatibility with Python 2.7.

I leave it up to the maintainers of this fine project to make the decision, but in my humble opinion, supporting Django 3.0 would be preferable to supporting Python 2.7 past the upcoming EOL.

[vdboor]

Thanks for your work! Django 3.0 support is fixed in 2.2.2!

I’ve used your PR’s as inspiration, but implemented it in a python2 compatible way so I could do a minor version bump instead of major release that drops compatibility (see f0176505f6b038d171dea7f2422be06751c22469)