Added error handling at import django.utils.six module. #758

[yukihira1992]

I fixed #758.
If django-storages ends support for Python2, close this.

[jschneier]

Thanks for this, I'm not quite sure why they removed six before 1.11 is no longer supported. I think a better way to solve this is to do try except rather than depending on six.

Want to take a crack at that?

[yukihira1992]

Removed six and added error handling.

[jdufresne]

I think it would be overall simpler maintenance to follow Django's lead and drop support for Python 2. It is very close to EOL anyway. It will required fewer compatibility shims and workarounds. Work for this has started #709

[codingjoe]

Thanks for addressing this issue. I guess it blocked some people from testing the Django alpha.

Thanks for this, I'm not quite sure why they removed six before 1.11 is no longer supported. I think a better way to solve this is to do try except rather than depending on six.

@jschneier I understand the confusion, yet six has undergone the regular deprecation cycle, which wasn't required, considering that it was never part of the official Django API.

I think it would be overall simpler maintenance to follow Django's lead and drop support for Python 2. It is very close to EOL anyway. It will required fewer compatibility shims and workarounds. Work for this has started #709

@jdufresne I second that. I believe there is no need to wait until 1.11 hits EOL in April, since 1.11 extended support does not cover Python 2.7 since it's EOL is in December. So one should only use Django 1.11 on Python 3 after December.

It's absolutely admirable to keep support Python 2 for that long, but I guess it's time for django-storages v2.0.0 ;)

[jschneier]

This library saw such a dearth of development for such a long time that I am attempting to put in all the minimum necessary features before doing something drastic and breaking backwards compat too strongly. When I release 2.0 I think we will also move to strict semantic versioning - given where we started I found it impractical to start there. I understand the EOL timeline, however.

[codingjoe]

@jschneier I hear you. If you need any help, you just say the word. Thanks for maintaining this beast, much appreciated.