On Tue, Jun 23, 2015 at 6:08 PM, Ashish Singla <[email protected]>
wrote:

> Hi Feng,
>     Quick question, Is there support for python 3.x in any upcoming
> release? and if yes, when is this release expected?
>
+Josh has been working on python recently and is probably the best person
to answer this.


>
> Best
> Ashish
>
>
> On Tuesday, October 21, 2014 at 7:31:04 PM UTC-4, Feng Xiao wrote:
>>
>> Hi all,
>>
>> I just published Protocol Buffers v2.6.1:
>> https://github.com/google/protobuf/releases/tag/2.6.1
>>
>> 2014-10-20 version 2.6.1:
>>
>>   C++
>>   * Added atomicops support for Solaris.
>>   * Released memory allocated by InitializeDefaultRepeatedFields() and
>>     GetEmptyString(). Some memory sanitizers reported them as memory
>> leaks.
>>
>>   Java
>>   * Updated DynamicMessage.setField() to handle repeated enum values
>>     correctly.
>>   * Fixed a bug that caused NullPointerException to be thrown when
>>     converting manually constructed FileDescriptorProto to
>>     FileDescriptor.
>>
>>   Python
>>   * Fixed WhichOneof() to work with de-serialized protobuf messages.
>>   * Fixed a missing file problem of Python C++ implementation.
>>
>> I'll soon upload it to Maven and pypi for Java and Python respectively.
>>
>> Cheers,
>> Feng
>>
>  --
> You received this message because you are subscribed to the Google Groups
> "Protocol Buffers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/protobuf.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Protocol Buffers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/protobuf.
For more options, visit https://groups.google.com/d/optout.

Reply via email to