#5511: Some tests don't are "unicodized"
-------------------------+--------------------------------------------------
Reporter: msaelices | Owner: nobody
Status: closed | Component: Unit test system
Version: SVN | Resolution: invalid
Keywords: | Stage: Unreviewed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
-------------------------+--------------------------------------------------
Changes (by mtredinnick):
* status: new => closed
* needs_better_patch: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_docs: => 0
Comment:
That is intentional in a number of cases. It's also not bad in the other
cases because they aren't returning non-ASCII data. That's one of the
guarantees we made when introducing the Unicode changes, that stuff like
that is safe. Until the need to be returning non-ASCII data, it's fine to
leave them as `__str__` methods.
--
Ticket URL: <http://code.djangoproject.com/ticket/5511#comment:1>
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
-~----------~----~----~----~------~----~------~--~---
