Hi, Dan,

I believe by "compatible" they mean compatible with the runtime. You
see, C extensions are prohibited in GAE. The patch changed
input_stream.py to fall-back to using arrays if buffers, which are
implemented in C, are not available. That said, it does not fix the
issue of restricted access to google.* packages. Because GAE does not
provide protobuf library by default (at least I haven't heard anything
yet) you have to bundle it with your application. At the same time,
the libs you bundle are not allowed to use google.* namespace, thus
the ImportError. The hack (http://code.google.com/p/protobuf-gae-hack)
seems still valid.



On Jul 2, 7:46 pm, Dan <danbr...@gmail.com> wrote:
> Hello-
> I'm working with GAE and ran into this error when trying to use
> protocol buffers:
> from google.protobuf import descriptor
> ImportError: No module named protobuf
> I saw some mention of people using hacks to do this in the past, but
> also saw that the release notes for protocol buffers v 2.10 said this:
> * Changes to input_stream.py should make protobuf compatible with
> appengine.
> I'm not sure what is meant by "compatible" in that statement, but I'd
> like to know if GAE still requires the hackery described in these
> threads referenced below. Is there an up-to-date howto or something
> like that somewhere that I missed?
> http://groups.google.com/group/protobuf/browse_thread/thread/6430dc5d...
> http://groups.google.com/group/google-appengine/browse_thread/thread/...
> Dan
You received this message because you are subscribed to the Google Groups 
"Protocol Buffers" group.
To post to this group, send email to protobuf@googlegroups.com
To unsubscribe from this group, send email to 
For more options, visit this group at 

Reply via email to