#25016: The related_name of ForeignKey cannot be Unicode name after Django 1.8
-------------------------------------+-------------------------------------
     Reporter:  sih4sing5hong5       |                    Owner:  nobody
         Type:  Bug                  |                   Status:  closed
    Component:  Database layer       |                  Version:  1.8
  (models, ORM)                      |
     Severity:  Release blocker      |               Resolution:  fixed
     Keywords:                       |             Triage Stage:  Accepted
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  1
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by Tim Graham <timograham@…>):

 In [changeset:"a97e50c5e6afe0ce2a8fb2ca27c88e57611b0053" a97e50c5]:
 {{{
 #!CommitTicketReference repository=""
 revision="a97e50c5e6afe0ce2a8fb2ca27c88e57611b0053"
 [1.8.x] Fixed #25016 -- Reallowed non-ASCII values for
 ForeignKey.related_name on Python 3.

 Backport of d3e12c901777697b7bf08b25e2dd46f0b951db8c from master
 }}}

--
Ticket URL: <https://code.djangoproject.com/ticket/25016#comment:10>
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/072.9e3bc29b748279801809122b7d7c6d10%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to