2009/1/29 bart van deenen bart.vandee...@gmail.com
Hi Kenton
Here's the details:
kubu:~$ protoc --version
libprotoc 2.0.3
kubu:~$ python -V
Python 2.5.2
This is a self-compiled protoc (because I had added the actionscript
output generator). I actually find in CHANGES.txt for 2.0.2
Petar, can you look into this?
2009/1/29 bart van deenen bart.vandee...@gmail.com
Hi Kenton
Here's the details:
kubu:~$ protoc --version
libprotoc 2.0.3
kubu:~$ python -V
Python 2.5.2
This is a self-compiled protoc (because I had added the actionscript
output generator). I actually
Hi Kenton
Here's the details:
kubu:~$ protoc --version
libprotoc 2.0.3
kubu:~$ python -V
Python 2.5.2
This is a self-compiled protoc (because I had added the actionscript
output generator). I actually find in CHANGES.txt for 2.0.2 that the
Strings now use the unicode type rather than the str
Oops found it already :-)
T.s=ustring.encode('utf-8')
and for getting it out
ustring2 = T.s.decode('utf-8')
Bart
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Protocol Buffers group.
To post to this group, send
On Jan 28, 7:50 pm, Kenton Varda ken...@google.com wrote:
What version of protocol buffers are you using? I believe we added unicode
support to Python protobufs in 2.0.1 or 2.0.2, in which case you shouldn't
need to manually encode/decode.
It's 2.0.3
I'm not at work right now, but will
