#13965: psycopg2 throws an "can't adapt" error on ugettext_lazy translated
strings
-------------------------------------------+--------------------------------
Reporter: mitar | Owner: nobody
Status: new | Milestone:
Component: Internationalization | Version: 1.2
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------------+--------------------------------
Comment (by mitar):
Replying to [comment:7 mk]:
> I'm not sure whether lazy strings should be automatically converted to
unicode on save(). I'd say this constitutes silent loss of information.
Ha? Lazy strings are just that - lazy. They should behave exactly the same
as strict strings, only their evaluation is postponed. This behavior
should be transparent, semantics should be the same. This should only have
influence on performance. So you can change strict into lazy and vice
versa without worrying that something will explode.
--
Ticket URL: <http://code.djangoproject.com/ticket/13965#comment:8>
Django <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.
