TypeError: Couldn't build proto file into descriptor pool! about protobuf HOT 10 CLOSED

If they all have different package names, they will not be considered as conflicts. Could you post the content of the .proto files and the exact error message you got?

from protobuf.

Such name conflict should be reported as an error in every implementation. The pure Python needs to be fixed to report an error as well.

from protobuf.

One problem is that in Python there isn't a central DecriptorPool with all generated types so it can't detect such conflicts. Unless such a DescriptorPool is introduced in Python, pure Python implementation won't be able to detect such conflicts. This also applies to Java.

from protobuf.

hi all,

any update of this issue? I also met this issue.

from protobuf.

Hi feiyuw, if you met this issue, the right solution is to get rid of the duplicated messages (by changing the name of one of them).

from protobuf.

hi @xfxyjwf , the proto difinition is included in the to decode file together with protobuf message, and the file format is out of my control, now I use python implementation instead of cpp to work around this problem.

from protobuf.

running into this issue too, dropping back to python implementation fixed it.

is the issue really that you can't have objects with the same name in separate .proto files? i have a common practice of defining Request & Response messages in different services and then import them in a common registry.

is the issue just that common registry?

from protobuf.

I think using the same name for different message types is not a good practice. In your case, you can set different package names on these .proto files and that will avoid the conflict.

from protobuf.

they all have different package names

from protobuf.

@xfxyjwf how u solved this problem

from protobuf.