I've made an attempt to create a Python3 compatible version of protobufs.
I have some code that passes pretty much all the unit tests which I've
posted here:
https://github.com/openx/python3-protobuf
I probably won't have a chance to look at this again for a couple weeks if
not longer, so I w
Python3, all
strings are unicode, so should this limit only exist in Python 2.x?
On Friday, September 21, 2012 6:16:41 PM UTC-7, Charles Law wrote:
>
> I've made an attempt to create a Python3 compatible version of protobufs.
> I have some code that passes pretty much all the unit te
I assumed that the type/value errors are no longer valid in Python 3, so I
removed the 3 checks in reflection_test.testStringUTF8Encoding(). All unit
tests now pass!
On Tuesday, September 25, 2012 1:47:09 PM UTC-7, Charles Law wrote:
>
> I thought about this a little, and realized tha
I have a python 3 version of protobufs that I want to test. It passes all
the unittests, so I know it can decode what it encodes, but I want to test
it that it can talk to clients written in other languages. I noticed when
I was making the python 3 version, I had some mistakes in the encoder t
nto the Riak library and change a bunch
of imports, for example import riak_pb2 --> import riak_py3_pb2 as riak_pb2.
On Monday, October 1, 2012 4:13:11 PM UTC-7, Charles Law wrote:
>
> I assumed that the type/value errors are no longer valid in Python 3, so
I did some work on this a few months back. If you search the mailing list
for python3 (no space) you can find the thread.
The work I did is pretty rough - it was mostly a proof on concept. I have
a repo that generates python3 files with the suffix pb2_py3. My code
passes all the unittests an
and 3.3. I
> have used a single-source approach (which is only really feasible starting
> with those two for syntax compatibility reasons).
>
> Python 2.4, 2.5 and I believe even 2.6 simply aren't going to work. It's
> too much effort.
>
> \malthe
>
> On Sat
I have the python 2.6+ & 3.2+ compatible code done. Search the mailing
list for python3 (no space) for more details.
On Thursday, March 7, 2013 1:05:59 PM UTC-8, Charles Law wrote:
>
> I did some work on this a few months back. If you search the mailing list
> for python3 (no s
I'd be interested in getting this done. I do want it merged in at some
point & this will only make it easier. Since I did some of the translation
at work I'm talking to legal about getting the contributor license
agreement signed. Free time is very rare though.
It might (not for sure, but ju
