#15404: "from __future__ import unicode_literals" in "settings.py"
----------------------------------------------------------------------------------+
Reporter: Andrej A Antonov (at Tower-39) <plm.tower39@…>
| Owner: nobody
Status: new
| Milestone:
Component: Uncategorized
| Version: 1.2
Resolution:
| Keywords:
Triage Stage: Unreviewed
| Has patch: 0
Needs documentation: 0
| Needs tests: 0
Patch needs improvement: 0
|
----------------------------------------------------------------------------------+
Changes (by lrekucki):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
Not all of those errors are related to unicode - most of them should
disappear on lastest 1.2.X version. I runned Django's full test suite with
{{{SECRET_KEY}}} being unicode and {{{DATABASES}}} containing unicode keys
and only errors I get are related to {{{SECRET_KEY}}}. IMHO, there is
anything to fix here, because {{{SECRET_KEY}}} ''should be'' a byte-string
- after all it's a series of random bytes.
Could you provide an easy way to reproduce an error related to DATABASES
setting ?
--
Ticket URL: <http://code.djangoproject.com/ticket/15404#comment:1>
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.
