New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate from django.utils.six to six #44
Conversation
Django #27753 has dropped six support Signed-off-by: Aleksi Häkli <aleksi.hakli@iki.fi>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right... I guess it's time to think about version support then.
(i.e. Shouldn't we just go Python 3 only, and bump the version number?)
I wouldn't drop Python 2 / Django 1.11 until both are EOL. We can drop Django < 1.11 though. |
We have dropped Python 2.x support in some places where the maintenance of Python 2.x code has made the code bases more difficult to develop. Here the support is already baked in and the project is very stable, though. IMO supporting Python 2.7 until the EOL is a nice thing to do unless it isn't a too big hassle. In this specific case it only requires adding the six dependency and changing one import. Our other package depends on django-appconf and requires it for testing against Django master, but at this moment the tests fail due to the missing six dependency. Cutting a new release that supports upstream Django would be awesome. Looking at the download ( |
Implement forwards compatibility for missing django.utils.six package imports on Django 2.2 Relates to django-compressor/django-appconf#44 and can be removed after django-appconf has received a new release which deprecates the use of the integrated Django six library Signed-off-by: Aleksi Häkli <aleksi.hakli@iki.fi>
Implement forwards compatibility for missing django.utils.six package imports on Django 2.2 Relates to django-compressor/django-appconf#44 and can be removed after django-appconf has received a new release which deprecates the use of the integrated Django six library Signed-off-by: Aleksi Häkli <aleksi.hakli@iki.fi>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, all makes sense. Thanks both.
Let's have this. I'll roll a new release (for Python 3.7 folks) this week.
Implement forwards compatibility for missing django.utils.six package imports on Django 2.2 Relates to django-compressor/django-appconf#44 and can be removed after django-appconf has received a new release which deprecates the use of the integrated Django six library Signed-off-by: Aleksi Häkli <aleksi.hakli@iki.fi>
Implement forwards compatibility for missing django.utils.six package imports on Django 2.2 Relates to django-compressor/django-appconf#44 and can be removed after django-appconf has received a new release which deprecates the use of the integrated Django six library Signed-off-by: Aleksi Häkli <aleksi.hakli@iki.fi>
Implement forwards compatibility for missing django.utils.six package imports on Django 2.2 Relates to django-compressor/django-appconf#44 and can be removed after django-appconf has received a new release which deprecates the use of the integrated Django six library Signed-off-by: Aleksi Häkli <aleksi.hakli@iki.fi>
Django #27753 has dropped six support
https://code.djangoproject.com/ticket/27753
django/django@4138481