#24927: django.utils.six and django.utils.encoding both define
python_2_unicode_compatible
-------------------------------------+-------------------------------------
Reporter: knbk | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Utilities | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by carljm):
I don't think it's worth putting users through a deprecation process on
the import location of `python_2_unicode_compatible`, when we could just
provide a non-deprecated import shim and leave it there until Python 2
support is dropped entirely. That's a lot of hassle for Django users in
order to save us a single import line in `django.utils.encoding`.
I do think it's good to switch to relying on the implementation in `six`.
--
Ticket URL: <https://code.djangoproject.com/ticket/24927#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/062.f43c093b3ed7c0fb9059fa1fb5a912cd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
