Is the advice in this thread, particularly with respect to generating C++
message implementations, still valid for modern versions of the Python
protobuf runtime?
Brief spelunking through the Python codebase didn't yield a clear mechanism
for how messages are automagically discovered.
On
On Tue, Dec 7, 2010 at 7:08 PM, Kenton Varda ken...@google.com wrote:
Cool. Serialization and parsing themselves should actually be improved even
more than that, but having other Python code around it waters down the
numbers. :)
The times are from a minimal microbenchmark using Python's
On Tue, Dec 7, 2010 at 9:19 PM, Yang Zhang yanghates...@gmail.com wrote:
Also, note that if you explicitly compile C++ versions of your
messages and link them into the process, they'll be even faster. (If you
don't, the library falls back to DynamicMessage which is not as fast as
Protobuf 2.4.0 will include an implementation of the Python API that is
backed by C++ objects. The interface is identical to the existing Python
API, and you can wrap it around existing C++ objects or have it construct
its own.
This code is already is SVN. Unfortunately the team is someone
Thanks Kenton, we'll take a look. Out of curiosity, any ETA on 2.4.0?
On Wed, Dec 1, 2010 at 12:04 PM, Kenton Varda ken...@google.com wrote:
Protobuf 2.4.0 will include an implementation of the Python API that is
backed by C++ objects. The interface is identical to the existing Python
API,
