[protobuf] python parsing failure, related either to repeated embedded message or enum-type therein

2010-06-16 Thread DFlo
t; is_connected: false status: CONNECTING } accounts { username: "dwflorek" protocol: "prpl-yahoo" is_connected: false status: CONNECTING } accounts { username: "dflo...@gxlinc.com" protocol: "prpl-jabber" is_connected: false

[protobuf] Re: python parsing failure, related either to repeated embedded message or enum-type therein

2010-06-16 Thread DFlo
log.error('readHandleServerMsg: Bad msg: %s' % e) # ... self._blockSize = 0 continue # the loop over handling the named-pipe and the buffered input log.debug('readHandleServerMsg: received msg:\n%s' % str(msg)) # ... I'll keep

[protobuf] Re: python parsing failure, related either to repeated embedded message or enum-type therein

2010-06-16 Thread DFlo
ield (and the "05" is the DISCONNECTED enum). In case that helps Thanks again, DFlo On Jun 16, 4:26 pm, DFlo wrote: > Entirely possible, but given that the expected number of bytes arrive > on the read-end of the pipe and get accumulated into a buffer, the > problem for thi

[protobuf] Re: python parsing failure, related either to repeated embedded message or enum-type therein

2010-06-16 Thread DFlo
Wow, don't I feel like an idiot ... on the sending side, strncpy != memcpy. Even though I allocated a big enough buffer, I didn't copy everything into it. I think I've embarrassed myself sufficiently for one day... As you were DFlo On Jun 16, 4:35 pm, DFlo wrote: >