On Wed, Mar 17, 2010 at 4:33 PM, Karen Tracey <kmtra...@gmail.com> wrote:
> On Wed, Mar 17, 2010 at 12:14 PM, Tom Evans <tevans...@googlemail.com>
> wrote:
>>
>> Any pointers?
>
> http://bugs.python.org/issue1288615
>
> It's fixed in current Python 2.6, I believe.
>
> However, this is a shell-only issue, so I'm not sure it will explain your
> original problem.
>
> Karen
>
Hmm, still a bit confused why it doesn't exhibit the issue under a
regular python 2.5 shell if it is a python 2.5 issue. Something
definitely 'tweaks' the environment going through the django shell
rather than the python shell. Must only be triggered in certain edge
cases, I suppose.
However, that does explain the failing tests. I am initiating one side
of the RPC from the shell, for testing, like so:
>>> checkBounceUser('10.0.0.1', {'X-Hi': u'£' }, sp=settings.SSO_ID)
which then prints out the extracted arguments in the console of the
other server:
name: X-Hi value: £
repr(name): u'X-Hi' repr(value): u'\xc2\xa3'
If I give it an explicit unicode codepoint, there isn't the parsing bug, and so:
>>> checkBounceUser('10.0.0.1', {'X-Hi': u'\xa3' }, sp=settings.SSO_ID)
name: X-Hi value: £
repr(name): u'X-Hi' repr(value): u'\xa3'
As always, garbage in => garbage out, so that explains why nothing I
was doing helped!
Thanks for the pointers Karen!
Cheers
Tom
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@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.
