I would suggest taking the parts you want most and adding them to the app engine environment. The differences and limitations of app engine make packages like sqlalchemy and beaker less effective. I bundled routes, the paste packages and pylons (and nose!) then stitched them together with the google webapp. It worked out pretty well.

The great part about pylons is that once you know the parts, you can combine them in any way you like.

Here's the script that starts a simple routes application on appengine.

from google.appengine.ext.webapp.util import run_wsgi_app

if __name__ == '__main__':
    from routing import make_map      #[1]
    from util import WSGIApplication  #[2]

    app = WSGIApplication(make_map(), debug=True)
    run_wsgi_app(app)


[1] The make_map method is the same as the standard pylons make map.
[2] The WSGIApplication takes a mapper which is used to match the url and dispatch to the appropriate app engine RequestHandler class. See pylons WSGIApplication for details.


Hope this is helpful.
  - Shailesh

On 07/01/2010 07:16 PM, Gio wrote:
Sorry I accidentally sent that!

I'm tempted to use GAE because I'd rather not get bogged down managing
servers and GAE seems to offer a convenient scaling paradigm (although
obviously you have to change your implementation techniques to get
that payoff).

I've been googling around and see a bunch of different ways to use
Pylons on the App Engine. Does anyone have a recommendation for the
best approach? Is it worth the annoyance of working in such restricted
environment?

Thanks for your help,
Gio.

On Jul 1, 10:12 pm, Gio<[email protected]>  wrote:
Hi,
I'm considering taking an existing Pylons application (although
probably only has like 20-30 hours of development time involved so
far) and switching the backend from MongoDB to GAE. The main reason
I'm tempted to do this that GAE


--
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