Comment #2 on issue 306 by matt.gi...@gmail.com: Python: Message objects
should not be hashable
http://code.google.com/p/protobuf/issues/detail?id=306
Ah, my apologies. I was using 2.3.0. It appears to be fixed for me
(Messages are now unhashable).
--
You received this message because you
Comment #11 on issue 296 by g...@google.com: Deploy protobuf-java 2.4.1 JAR
to Maven Repository
http://code.google.com/p/protobuf/issues/detail?id=296
And a well-deserved bump. We had some stuff going on around here that kept
me busy… :-) I'll start the build now.
--
You received this
Status: New
Owner: liuj...@google.com
Labels: Type-Defect Priority-Medium
New issue 309 by inf...@gmail.com: Support for C-style comments in
editors/proto.vim
http://code.google.com/p/protobuf/issues/detail?id=309
proto.vim doesn't currently highlight C-style comments (/* ... */)
in .proto
Updates:
Status: Fixed
Labels: FixedIn-2.4.0
Comment #1 on issue 306 by jas...@google.com: Python: Message objects
should not be hashable
http://code.google.com/p/protobuf/issues/detail?id=306
This was already fixed in 2.4.0 - are you using an older version of the
library?
You could always extend the compiler, but I bet you could get away with a
simple preprocessor that aliases types and represents those larger integers as
raw bytes.
--Chris
On Jun 30, 2011, at 7:30 AM, Eric Hopper wrote:
> I'm building an application around protocol buffers. The types in my
>
On Jun 27, 12:33 pm, Ruslan Mullakhmetov wrote:
> Hi
>
> I'm trying to deserialize different protobuf messages in python. Is the
> any way to get message type from unserialized message?
>
> Like dynamic message in cpp and java ?
Presumably you're using the pattern where you have a containin
I'm building an application around protocol buffers. The types in my
application can be mapped to types that protocol buffers supports, so
I can sort of on-the-fly translate. For example, I have a timestamp
field that can be translated to a 64 bit unsigned integer. But it
would be really nice to do
Status: New
Owner: liuj...@google.com
Labels: Type-Defect Priority-Medium
New issue 308 by 0902h...@gmail.com: unresolved external symbol
kEmptyString when linking protobuf as a dll.
http://code.google.com/p/protobuf/issues/detail?id=308
What steps will reproduce the problem?
1.compile protob
Comment #10 on issue 296 by jhuxh...@googlemail.com: Deploy protobuf-java
2.4.1 JAR to Maven Repository
http://code.google.com/p/protobuf/issues/detail?id=296
*End-Of-Month-Bump*
--
You received this message because you are subscribed to the Google Groups "Protocol
Buffers" group.
To post t
