Broken by protobuf 2.4.0's native Python feature

[GoogleCodeExporter]

We're using PB 2.4.0 (not yet released at this time) for its substantially 
faster native Python protobufs.

When using the native Python protobufs (set the env var 
PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=cpp), protobuf-socket-rpc gives us the 
following against the current protobuf svn HEAD (r352):

...
  File "/home/yang/work/pod/env/lib/python2.6/site-packages/protobuf/__init__.py
", line 22, in <module>
    from service import RpcThread, RpcService
  File "/home/yang/work/pod/env/lib/python2.6/site-packages/protobuf/service.py"
, line 39, in <module>
    from protobuf.channel import SocketRpcChannel
  File "/home/yang/work/pod/env/lib/python2.6/site-packages/protobuf/channel.py", line 41, in <module>
    import rpc_pb2 as rpc_pb
  File "/home/yang/work/pod/env/lib/python2.6/site-packages/protobuf/rpc_pb2.py", line 104, in <module>
    options=None),
  File "/home/yang/work/protobuf-read-only/python/google/protobuf/descriptor.py", line 400, in __init__
    self._cdescriptor = cpp_message.GetFieldDescriptor(full_name)
  File "/home/yang/work/protobuf-read-only/python/google/protobuf/internal/cpp_message.py", line 58, in GetFieldDescriptor
    return _pool.FindFieldByName(full_field_name)
TypeError: Couldn't find field protobuf.socketrpc.Request.service_name

Not really sure how big the compatibility break is, but hopefully it requires 
only minor tweaks in protobuf-socket-rpc.

Original issue reported on code.google.com by yanghate...@gmail.com on 1 Dec 2010 at 9:48