[google-appengine] Deleting props: this works, but is it safe?

To remove deleted properties from the datastore, GAE docs suggest this: https://developers.google.com/appengine/articles/update_schema It boils down to re-defining your class hierarchy as Expando, fetch, call delattr, put, then changing model back. What I've noticed is that even when you remove

[google-appengine] Google Cloud Storage Client not working on dev appserver (no _ah/gcs handler?)

I didn't post this q on SO, but I'm running into the same issues. http://stackoverflow.com/questions/19727344/google-cloud-storage-client-not-working-on-dev-appserver It looks like the latest version of the GCS client is posting requests to /_ah/gcs, but no one's home on the other side (404).

[google-appengine] What am I missing about dev_appserver2 and push task queues?

doing this for me? Thanks! -ckhan -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send

[google-appengine] Safe to call ndb tasklet get_result() in a tasklet?

From the NDB async docs: Furthermore, instead of using acct = key.get() or acct = key.get_async().get_result(), the function should useacct = *yield* key.get*_async*(). This yield tells NDB that this is a good place to suspend this tasklet and let other tasklets run. Re the second example:

[google-appengine] Understanding Request was aborted after waiting too long

that should be reported GAE prod) Thanks so much for any comments/pointers/responses. -ckhan -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/VkTImu2ALmAJ

Re: [google-appengine] Re: ndb, deadlock waiting for flush, and maximum recursion in app_logging

and greatly appreciated. -ckhan On Tuesday, October 30, 2012 4:05:55 PM UTC-7, Guido van Rossum wrote: On Tue, Oct 30, 2012 at 2:54 PM, ckhan charl...@gmail.com javascript: wrote: Hi Guido - Thanks, this was exactly the case! I was indeed mixing sync/async calls in a tasklet

[google-appengine] Re: ndb, deadlock waiting for flush, and maximum recursion in app_logging

munch_stuff in conjunction with 'deferred'? It would seem that marking it with a toplevel/tasklet decorator isn't enough (deferred complains about failing to pickle the function). Or, would this configuration be unsupported by deferred? Thanks again! -ckhan On Tuesday, October 30

[google-appengine] ndb, deadlock waiting for flush, and maximum recursion in app_logging

points in the code path. Is that correct? The recursion depth error seems to come from the app_logging. But is that the underlying cause, or the symptom of the failure? If the latter, how do I narrow what got me into this situation? Any help much appreciated. -ckhan -- You received

[google-appengine] Question about query equality operator docs

/appengine/docs/python/datastore/queryclass.html#Query_filter use '=' q.filter(last_name =, Smith) My experiments seem to indicate that either will work. Is the table just a typo, or is there a difference? -ckhan -- You received this message because you are subscribed to the Google Groups Google