On Dec 17, 2011 10:12 PM, "Yo-Yo Ma" <baxterstock...@gmail.com> wrote:
>
> Is this a prank, or is there really going to need to be a u('') for
> every u'' (of which there are thousands, since everything is Unicode
> in Django) in my Django apps, in order to use P3K? Removing the "u" is
> one thing, but adding another text function seems absurd, no?
>
> name = models.CharField(_(u('name'))). # eek :/The plan is to drop Python 2.5 support on the same timeline as merging this, so no, you won't need to do that, since 2.6+ support the Python 3 literal syntax with a __future__ import. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
