View Single Post
Old 03-08-2014, 01:51 AM   #19
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,476
Karma: 8025702
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by kovidgoyal View Post
The only difference that I can see between the ajax routes and the rest are that the ajax routes are unicode strings, the rest are not, (because of the from __future__ import unicode_literals in ajax.py)

Presumably, changing those strings to bytestrings should fix it, though given that I dont understand what the bug in routes is, I have no way to be sure.
This is why I was asking about languages. I was wondering if we had some character encoding issue that prevented all that string manipulation in buildfullreg from working.
chaley is offline   Reply With Quote