Oh man! This is like Pipelines "Lite"! I love it :D Some early feedback on the Count example -
It seems odd to start your promises in the constructor, technically before you know that 'put' has completed. It's possible that the tasks trigger before the entity is saved. [now obviously, this may have been intended, because your just saving a count result - it's meant to count large numbers of entities, but what if that count is 0 ;D] This is a case where I'd leverage transactional task saves with the entity put. :) [but I don't know enough about the underlying architecture to know whether or not you require task names] Anyway, exciting! ps your article didn't mention pipelines, which are an incredibly useful asset: https://github.com/GoogleCloudPlatform/appengine-pipelines On Thursday, November 20, 2014 7:43:49 PM UTC-8, Emlyn wrote: > > Hi AppEngine Pythonistas, > > I've written a useful library for distributed processing in AppEngine, > implementing distributed promises. They're described in detail in this > post: > > https://point7.wordpress.com/2014/11/21/distributed-promises-for-appengine/ > > I want to open source the library, can anyone help me with best > practices for creating an open source python package, including how to > make that most easily accessible to appengine developers? > > -- > Emlyn > > http://point7.wordpress.com - My blog > https://plus.google.com/u/0/100281903174934656260 - Google+ > -- 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 email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout.
