thrift-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matthew Chambers <>
Subject Re: thrift compile to CPython objects?
Date Wed, 24 Apr 2013 21:20:15 GMT

We're writing out C++ and then wrapping it with Cython not only for 
speed, but to provide a more pythonic API.

On 25/04/13 07:30, Randy Abernethy wrote:
> Hello John,
> Have you guys tried the fastbinary protocol or twisted?
> Having the Thrift compiler emit C++ to compile into a Python library with
> PyObjects for the Client/Server stubs and structs would be interesting.
> These could in turn use the existing C++ lib for protocols and transports
> making everything after the method call on the Python client compiled
> code. There is no such support in the Thrift main branch but it is 
> possible
> someone somewhere has done it, though I have not see such a thing. Would
> be great to hear how it works for you guys if you take a crack at it.
> Regards,
> Randy
> On 4/24/2013 4:25 AM, John R. Frank wrote:
>> Thrift Developers,
>> We have noticed that reading (deserializing) messages in python is 
>> ~100x slower than deserializing the exact same data in C++. Is this 
>> expected? (I can provide examples, if useful.)
>> Is there a better compilation flag to use than py:new_style,slots
>> Seems like it would be possible/useful to compile directly to 
>> PyObject structures
>> Does this exist or has anyone looked into it?
>> jrf

View raw message