-
Notifications
You must be signed in to change notification settings - Fork 59
Added support for Google App Engine runtime #24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
|
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. |
|
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 |
|
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:
|
|
@rcarmo let me know if you need any more testing on App Engine. |
|
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 :)