#4161: [unicode] Convert oldforms
----------------------------------------------------------+-----------------
Reporter: Ivan Sagalaev <[EMAIL PROTECTED]> | Owner:
mtredinnick
Status: new |
Component: Uncategorized
Version: other branch |
Resolution:
Keywords: unicode |
Stage: Unreviewed
Has_patch: 1 |
Needs_docs: 0
Needs_tests: 0 |
Needs_better_patch: 0
----------------------------------------------------------+-----------------
Comment (by mtredinnick):
Yeah, I don't know what to do about "existing admin". Actually, I think
I'm going to have to convert it, because we'll be ready first (and the
existing i18n string problems are hurting people). However, I am going to
leave it until the absolutely last thing to do so that there's still a
chance it won't need to be done.
Patch itself looks good. In `django/oldforms/__init__.py`, is the explicit
use of
{{{
#!python
unicode(self).encode('utf-8')
}}}
rather than smart_string(self) because you like messing with my head or
for a good technical reason? I don't really mind -- so don't bother
changing it -- since I suspect there's no difference here, but the fact
that you are writing it this way makes me think you are doing it for a
reason.
--
Ticket URL: <http://code.djangoproject.com/ticket/4161#comment:3>
Django Code <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 [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
-~----------~----~----~----~------~----~------~--~---
