#15404: "from __future__ import unicode_literals" in "settings.py"
----------------------------------------------------------------------------------+
Reporter: Andrej A Antonov (at Tower-39) <plm.tower39@…>
| Owner: nobody
Status: closed
| Milestone:
Component: Uncategorized
| Version: 1.2
Resolution: wontfix
| Keywords:
Triage Stage: Unreviewed
| Has patch: 0
Needs documentation: 0
| Needs tests: 0
Patch needs improvement: 0
|
----------------------------------------------------------------------------------+
Changes (by russellm):
* status: new => closed
* resolution: => wontfix
Comment:
We natively support unicode, but we don't natively support Python 3 (at
least, not yet). The {{__future__}} call you describe exists specifically
as a Python 3 migration aid.
This will become a legitimate bug when we actually claim some level of
Python 3 support, but until then, I'm going to mark this wontfix.
--
Ticket URL: <http://code.djangoproject.com/ticket/15404#comment:2>
Django <http://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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
