[protobuf] Re: Issue 454 in protobuf: Python API parallel read access is not thread safe when repeated fields are empty

2013-02-27 Thread protobuf
Comment #4 on issue 454 by johannes...@googlemail.com: Python API parallel read access is not thread safe when repeated fields are empty http://code.google.com/p/protobuf/issues/detail?id=454 But that's a severe violation of the documented behavior if the message classes in fact aren't thre

[protobuf] Re: Issue 454 in protobuf: Python API parallel read access is not thread safe when repeated fields are empty

2013-02-27 Thread protobuf
Comment #3 on issue 454 by xiaof...@google.com: Python API parallel read access is not thread safe when repeated fields are empty http://code.google.com/p/protobuf/issues/detail?id=454 I have had a look at this problem before. There are several places where _fields.iteritems() is used. I am

[protobuf] Re: Issue 454 in protobuf: Python API parallel read access is not thread safe when repeated fields are empty

2013-02-27 Thread protobuf
Comment #2 on issue 454 by johannes...@googlemail.com: Python API parallel read access is not thread safe when repeated fields are empty http://code.google.com/p/protobuf/issues/detail?id=454 Any ideas on this? Actually I would have expected that such a bug will make it into the next releas

[protobuf] Re: Issue 454 in protobuf: Python API parallel read access is not thread safe when repeated fields are empty

2013-01-17 Thread protobuf
Updates: Cc: f...@google.com Comment #1 on issue 454 by liuj...@google.com: Python API parallel read access is not thread safe when repeated fields are empty http://code.google.com/p/protobuf/issues/detail?id=454 Adding Frank to take a look. -- You received this message because you a