Thanks Jason, this resolves the issue.
I actually have separate directories for the protobuf code as well as my
own. I use the '-I' option when calling protoc, which I pointed at the
directory containing 'descriptor.proto'. When I moved that path up two
directories and made the import statement
Thanks for the update Jason. I'll make sure to iterate over the directory
and call FindFileByName() on each .proto I plan to use
On Monday, June 4, 2012 4:06:39 PM UTC-7, Jason Hsueh wrote:
>
> This is a result of SourceTreeDescirptorDatabase not implementing
> FindFileContainingSymbol() - it do
Any new process of this issue? .
On Monday, September 26, 2011 9:12:09 PM UTC+8, kyo...@gmail.com wrote:
>
> when you running The C++ implementation for Python.
>
> >>> from proto import test_pb2
> >>> r = tes_pb2.SkillResult()
> >>> import gc
> >>> gc.set_debug(gc.DEBUG_LEAK)
> >>> gc.garba
I see, yeah, you typically want to have the include path for protoc by the
root of your source tree, rather than enumerating all the different
subdirectories you want to include. I'll make a note to find a place in the
documentation to mention this; this seems to come up pretty frequently.
On Tue,
I am a beginning programmer trying to install the Python Protocol
Buffers from this package:
http://code.google.com/p/protobuf/downloads/detail?name=protobuf-2.4.1.zip
I'm staring at the readme, and I have added both python and version
2.4.1 of protoc.exe into my PATH. However, when I try to run