#393: [patch] Filters don't take the str() value of a var
-------------------------+--------------------------------------------------
Reporter: Boffbowsh | Owner: adrian
Status: new | Component: Core framework
Version: | Resolution:
Keywords: | Stage: Ready for checkin
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
-------------------------+--------------------------------------------------
Comment (by Marc Fargas <[EMAIL PROTECTED]>):
I would rather set "Design decission needed" and let some core developer
decide if the smart_string() function on the patch should support unicode
before checkin (in favour of #2489) or if it's ok for now to be checked
in.
But also, the bug should be fixed, so "Ready for chekin" is ok! But can I
suggest opening a new ticket about adding unicode support to
smart_string() when this one gets closed?
--
Ticket URL: <http://code.djangoproject.com/ticket/393#comment:18>
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
-~----------~----~----~----~------~----~------~--~---
