#12769: Pickle fails if fields have lazy verbose name translations
---------------------------------------------------+------------------------
Reporter: jtiai | Owner: nobody
Status: new | Milestone:
Component: Database layer (models, ORM) | Version: SVN
Resolution: | Keywords: orm pickle
query
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by jholloway7):
* cc: jholloway7 (added)
Comment:
I have noticed that this is also an issue if you use `ugettext_lazy` in
the `choices` argument for a `CharField`:
{{{
#!python
my_field = models.CharField(max_length=10, choices=(('1', _('Choice1')),
('2', _('Choice2'))))
}}}
I don't think the proposed patch would address this, but I admit that I
don't understand why this declarative stuff is even getting pickled --
i.e. whether it's worth patching at this level or there's some overarching
issue to address.
--
Ticket URL: <http://code.djangoproject.com/ticket/12769#comment:4>
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.
