Mike Verdone wrote: > Ideally Google should provide empty modules for all Python std lib > stuff. It looks like they've already built a few empty modules like > socket, I'd imagine to keep Django or some related piece of code > happy.
I've started doing this in a small way: http://code.google.com/p/appengine-monkey/ With this, Pylons mostly loads up, except for Mako. I'm not sure how to disable the templating plugin entirely, as that would be the best way to move forward from here. Mako might work eventually, but not very soon. > In the meantime it looks like sys.meta_path is available to play with > in AppEngine. We could throw an importer in there that returns empty > "stub" modules for all the missing standard lib modules. This way we > can at least keep the mess in a single import fixer module until the > modules are made available in AppEngine. > > Check out http://mike.verdone.ca/pymisc/appengine/stub_importer.py > > It's the simplest thing that works. So long as you import that module > before anything else, and provide an empty module named "stub", you > can import anything in the STUB_MODULES list and it won't complain. > > In other news, AppEngine's pastel purple, heliotrope, and pink > tracebacks are rather charming. It's just the default styling of the stdlib cgitb module. A somewhat peculiar aesthetic. It's not installed by default in the production environment, just on the dev server. -- Ian Bicking : [EMAIL PROTECTED] : http://blog.ianbicking.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-devel@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-devel?hl=en -~----------~----~----~----~------~----~------~--~---
