2011/10/18 Greg Stein <gst...@gmail.com>: >> "The unicode problem"[1][2] >> makes it rather unusable for me with Python 2.7. :( (Not due to your >> changes, but the Riak Python client in general) >> >> [1]: https://issues.basho.com/show_bug.cgi?id=649 >> [2]: https://github.com/basho/riak-python-client/issues/32 > What is it about 2.7 that makes the problem worse for you? Are you > using Unicode keys or bucket names?
(I just noticed I somehow managed to only send my response to Greg, so reposting) No, I'm not using unicode names at all. It's just that the json implementation in Python 2.7 always yields unicode objects (unlike simplejson with sometimes gives str objects and sometimes unicode objects). Let me extract some code examples that triggers it. (A little later) Hrm.. Maybe my use cases are odd ball. Anything that involves Riak search is busted[1], and it seems all the code I've been messing with lately was using Riak Search in some way or form, so it feels very debilitating. To work around it, I've hacked the riak client to str()ify these things, which works great for me, since I know I'll never do unicode keys or buckets, but I understand it's not generally applicable. [1]: https://gist.github.com/1296384 -- Soren Hansen | http://linux2go.dk/ Ubuntu Developer | http://www.ubuntu.com/ OpenStack Developer | http://www.openstack.org/ _______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
