On Apr 9, 2008, at 9:43 AM, Bob Ippolito wrote:
> You can always take the approach where C modules are used if
> available, otherwise pure Python code can be used. simplejson does
> this, for example.
Unfortunately it's not just C extensions that are the problem on app
engine, it's actually Python builtin modules written in C.
E.g. the problem with Mako and Genshi on app engine is that they need
the builtin parser module to parse python code to AST. Rumor has it
some C modules, like parser, are restricted due to security concerns
-- like they would need to audit the parser module's rather hairy C
code to ensure it's not violating their restricted Python sandboxing
(though I'm not sure about this).
I'm getting the impression that the guys behind google app engine are
very Django centric, and might not be that aware of how important
Mako and Genshi are outside of Django (I think they're very important
for Django too, not every Django app uses Django templates).
I'd encourage everyone to help make them aware of how important it is
to get the pieces of our stack working: one way is by voting
('starring', click on the star) the related issues logged on their
ticket tracker:
The Mako templating doesn't work:
http://code.google.com/p/googleappengine/issues/detail?id=9
Incompatible with pkg_resources
http://code.google.com/p/googleappengine/issues/detail?id=60
Expand Python framework support to Zope3, Turbogears, and Pylons
http://code.google.com/p/googleappengine/issues/detail?id=33
--
Philip Jenvey
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To post to this group, send email to pylons-discuss@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---
