Added support for Google App Engine runtime - #24
Conversation
alex
commented
Apr 14, 2014
I'm pretty down on needing a bunch of GAE specific memcached hacks, it seems like a real abstraction failure for a parsing library to have to know thigns like this. I'd much rather just allowing the user to disable caching altogether. |
paultag
commented
Apr 14, 2014
alex
commented
Apr 14, 2014
One thing I'd be open to is some sort of abstraction for teh caching, like On Mon, Apr 14, 2014 at 10:35 AM, Paul Tagliamonte <notifications@github.com
"I disapprove of what you say, but I will defend to the death your right to |
rcarmo
commented
Apr 14, 2014
I'm fine either way - this works for me now, but I grant it's more expedient than clean :) Maybe it could be merged in temporarily until a better abstraction is put in place? Either way, only the parser generator is affected, and only inside the one scope. It's a fairly localized change. R. On 14 Apr 2014, at 15:37 , Alex Gaynor notifications@github.com wrote:
|
proppy
commented
Apr 16, 2014
@rcarmo let me know if you need any more testing on App Engine. |
rcarmo
commented
Apr 16, 2014
I'm working on https://github.com/rcarmo/rss2imap-gae - still getting started, but it seems to work OK in the SDK. On 16 Apr 2014, at 22:17 , Johan Euphrosine notifications@github.com wrote:
|
This pull request allows rply to run inside Google App Engine. I'm tagging @paultag and @olasd here so that they can consider getting rid of their hylang-specific fork :)