Open rcarmo opened 10 years ago
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.
Oh yeah, we dropped the fork, but this would be great! I know a few folks are trying to use Hy on GAE (like @proppy) -- so we'd love to work with @alex to make this work the right way upstream :)
One thing I'd be open to is some sort of abstraction for teh caching, like jinja2 has, so that someone else can write the GAE integration.
On Mon, Apr 14, 2014 at 10:35 AM, Paul Tagliamonte <notifications@github.com
wrote:
Oh yeah, we dropped the fork, but this would be great! I know a few folks are trying to use Hy on GAE (like @proppy https://github.com/proppy) -- so we'd love to work with @alex https://github.com/alex to make this work the right way upstream :)
— Reply to this email directly or view it on GitHubhttps://github.com/alex/rply/pull/24#issuecomment-40372440 .
"I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire) "The people's good is the highest law." -- Cicero GPG Key fingerprint: 125F 5C67 DFE9 4084
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:
One thing I'd be open to is some sort of abstraction for teh caching, like jinja2 has, so that someone else can write the GAE integration.
On Mon, Apr 14, 2014 at 10:35 AM, Paul Tagliamonte <notifications@github.com
wrote:
Oh yeah, we dropped the fork, but this would be great! I know a few folks are trying to use Hy on GAE (like @proppy https://github.com/proppy) -- so we'd love to work with @alex https://github.com/alex to make this work the right way upstream :)
— Reply to this email directly or view it on GitHubhttps://github.com/alex/rply/pull/24#issuecomment-40372440 .
"I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire) "The people's good is the highest law." -- Cicero GPG Key fingerprint: 125F 5C67 DFE9 4084 — Reply to this email directly or view it on GitHub.
@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:
@rcarmo let me know if you need any more testing on App Engine.
— Reply to this email directly or view it on GitHub.
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 :)