#21934: Missing import statements (e.g. unicode literals)
------------------------------------+--------------------------------------
Reporter: david.fischer.ch@… | Owner: nobody
Type: Bug | Status: closed
Component: Uncategorized | Version: master
Severity: Normal | Resolution: needsinfo
Keywords: unicode,i18n | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------------+--------------------------------------
Changes (by aaugustin):
* resolution: invalid => needsinfo
Comment:
I wouldn't call that bug "invalid". It's true that we I dropped the ball
mid-way with regard to unicode_literals while porting to Python 3.
I stopped when I reached code that wasn't well tested, mostly in
django.contrib.gis, because adding unicode_literals created actual bugs.
Adding unicode_literals to every file isn't an option. It would trigger a
slew of regressions.
That said, we should continue adding unicode_literals when we have the
opportunity, which means, when we add tests.
Re-closing "needsinfo", please provide the stack trace for the problem you
encountered and reopen.
--
Ticket URL: <https://code.djangoproject.com/ticket/21934#comment:2>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/084.7f195c5db23923c50c9364c479a73247%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
