Hi all.  I've been working on a project to provide some of the 
functionality that is missing from the App Engine environment:

   http://code.google.com/p/appengine-monkey/

Currently this fairly modest set of functions and a couple modules. 
Some of the modules provided (like subprocess) aren't actually 
*working*, but this makes the module importable for cases where a 
library imports a module, but only uses that module in a couple 
functions, and there's other parts of the library that are still useful.

This also makes Setuptools functional, and by association Pylons.

The current state of Pylons is that the Mako trunk is working and the 
session handling (provided in the Beaker trunk) supports the Datastore 
as a backend.  So Pylons basically works, though with the caveat that it 
hasn't been tested much.

Full instructions for starting a Pylons application are located here:

   http://code.google.com/p/appengine-monkey/wiki/Pylons

I also welcome contributors to appengine-monkey.  If you are interested 
in implementing layers on urlfetch to be compatible with httplib, 
urllib, or urllib2, that would be well within the scope of this project.

(BTW, my blog post describing mostly the same things as this email is 
here: http://blog.ianbicking.org/2008/04/13/app-engine-and-pylons/)

-- 
Ian Bicking : [EMAIL PROTECTED] : http://blog.ianbicking.org

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To post to this group, send email to [email protected]
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to