#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: Design decision needed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------+------------------------------
Changes (by mk):
* stage: Unreviewed => Design decision needed
Comment:
No, semantics aren't the same. A lazy i18n string depends on the context
and this is lost when the string is stored in a DB. I'll rather be warned
(with an explosion, if it has to be) when I try doing something stupid.
"Silent data loss" is a strong description for what's happening if a lazy
string is translated upon entering storage, but I'd still argue that's
what is happening here. And silent data loss is bad(tm).
I'll mark this design decision needed, hopefully someone from core will
weigh in on this issue.
--
Ticket URL: <http://code.djangoproject.com/ticket/13965#comment:9>
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.
