#16299: Django model-module doesn't support unicode_literals
-------------------------------------+-------------------------------------
Reporter: | Owner: nobody
martijn.bastiaan@… | Status: closed
Type: Bug | Component: Database layer
Milestone: | (models, ORM)
Version: SVN | Severity: Normal
Resolution: fixed | Keywords: unicode,
Triage Stage: Accepted | ForeignKey, AttributeError
Needs documentation: 0 | Has patch: 1
Patch needs improvement: 0 | Needs tests: 0
UI/UX: 0 | Easy pickings: 1
-------------------------------------+-------------------------------------
Comment (by russellm):
In [16675]:
{{{
#!CommitTicketReference repository="" revision="16675"
[1.3.X] Fixed #16299 -- Ensure that unicode strings can be used to
identify classes in ForeignKey and ManyToManyFields. Unicode strings
aren't actually legal as class names, but this is an issue if you use from
__future__ import unicode_literals in your models.py file. Thanks to
Martijn Bastiaan for the report, and Anthony Briggs for the final patch.
Backport of r16663 from trunk.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/16299#comment:5>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
