Hi Jano,
I never tried it myself and I always though it's experimental feature and
not very well tested. Could you create an issue on github
(https://github.com/GreatFruitOmsk/protobuf-py3/issues) ?
I'm planning to down integrate all changes from current repository (they
pushed a lot of
Ilya, any ideas what's needed to make
PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=cpp work with Python3?
http://yz.mit.edu/wp/fast-native-c-protocol-buffers-from-python/
On Thursday, April 17, 2014 5:44:05 PM UTC+2, Ilya Kulakov wrote:
The project now passes tests for Python 2.4-2.7 and 3.1-3.4.
The project now passes tests for Python 2.4-2.7 and 3.1-3.4. Probably for
Python 3.0 as well, but it's not available for my Linux distro.
https://github.com/GreatFruitOmsk/protobuf-py3/releases/tag/2.5.1-pre
среда, 16 апреля 2014 г., 17:40:28 UTC+7 пользователь Ilya Kulakov написал:
Repo was
Repo was moved to https://github.com/GreatFruitOmsk/protobuf-py3
суббота, 12 апреля 2014 г., 16:44:44 UTC+7 пользователь Ilya Kulakov
написал:
Here is my attempt to port protobuf 2.5.0 to py3k based on Kirill's
pathces: https://github.com/GreatFruitOmsk/python3-protobuf
Binary release and
Here is my attempt to port protobuf 2.5.0 to py3k based on Kirill's
pathces: https://github.com/GreatFruitOmsk/python3-protobuf
Binary release and the python
module: https://github.com/GreatFruitOmsk/python3-protobuf/releases/tag/2.5.0
--
You received this message because you are subscribed to
On Saturday, April 12, 2014 6:05:56 AM UTC+1, Ilya Kulakov wrote:
What's the purpose of all these WIN32 ifdefs? I didn't have problems
compiling protobuf for windows.
I was using my own project files where I was trying to avoid as many
compatibility-related defines as possible. For
Hi Kirill,
Please post a diff. I'll apply it and make Pull Request to Charles' repo.
воскресенье, 16 марта 2014 г., 3:41:20 UTC+7 пользователь Kirill Bogdanov
написал:
I've ported Charles Law's work to a recent protobuf (version 519). It
passes tests on Win7 x86_64 with Python 3.3 and 2.7.
The diff is in my first message from Mar 15, perhaps I should simply delete
the second one which I posted because the first one not appear in the
thread for a few days.
--
You received this message because you are subscribed to the Google Groups
Protocol Buffers group.
To unsubscribe from
What's the purpose of all these WIN32 ifdefs? I didn't have problems
compiling protobuf for windows.
суббота, 12 апреля 2014 г., 8:28:29 UTC+7 пользователь Kirill Bogdanov
написал:
The diff is in my first message from Mar 15, perhaps I should simply
delete the second one which I posted
I've ported Charles Law's work to a recent protobuf (version 519). It
passes tests on Win7 x86_64 with Python 3.3 and 2.7. Could post a diff
against svn checkout if you are interested.
--
You received this message because you are subscribed to the Google Groups
Protocol Buffers group.
To
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
On Thursday, August 22, 2013 2:36:07 PM UTC-7, Charles Law wrote:
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
Charles,
Thanks for taking the time to do this! Is it possible to make your
github repo be based off of the latest svn checkout of GPB? I have used
the instructions here [0] to do this for other projects where I wanted to
use git but the official code was managed with svn (as in this case).
I have been doing the same thing over the last week. At PyCon Barry
Warsaw, Lennart Regebro, and several others held a porting from 2 to 3
clinic where I got some really great tips. They answered all the issues I
thought would be hard, and I figured I should do the updates while the
fixes
I have completed this work: https://github.com/malthe/google-protobuf.
– in as much as that all tests run without fail on both 2.7 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
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 that both
I thought about this a little, and realized that both unicode and str type
strings are passed into fields that have cpp_type CPP_STRING and field_type
TYPE_STRING. I know the 7-bit character limit is only imposed on str type
strings - all the extreme value tests use unicode strings. In
17 matches
Mail list logo
