On 2011-08-23, at 1:08 AM, Leon van der Ree wrote:
> that explains why I experience this issue. However doesn't it suppose
> to work like this; Why should a safe string become unsafe again after
> deserialisation? I understand this is a current limitation of the
> serialisation process, but this is not exactly what you would expect,
> is it. So in my eyes this is still a bug.
Nothing advertises it would work this way, so its a feature request.
> Are there any known workarounds?
You could store more than a string in the message I bet, for example
{'msg':'hello', 'safe':True} and then cope with it when you deserialize.
--
Andy McKay
a...@clearwind.ca
twitter: @andymckay
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
