On Sat, May 2, 2009 at 6:34 AM, David Wilson <[email protected]> wrote: > > Hi > > My studio is currently evaluating Pylons (amoung Django, CherryPy, and > an inhouse extended version of WebApp) for a high traffic web > application we wish to run on GAE. Out of the web frameworks available > I feel Pylons would be particularly suitable due to its modular > approach. > > I had a few issues getting appengine-monkey to run on Windows which I > documented here > > http://code.google.com/p/appengine-monkey/issues/detail?id=19 > > > Which leads to the questions: > > 1) What does not work / has issues on GAE in Pylons 0.9.7 > > I could not seem to get the debugger to work (vital for consideration) > > 2) Is GAE a supported platform in the future for Pylons? > > i.e. is a version on the horizion that will have full functionality on > a project build with a -gae switch, without the need for 3rd party > patchs etc.
That's actually Google's responsibility, not Pylons'. Buty App Engine SDK 1.2.1, released this month, has the Setuptools support so appengine-monkey is no longer necessary. I've started an appengine-homedir project that's based on appengine-monkey but without the monkey. http://bitbucket.org/sluggo/appengine-homedir/ I'll be testing it more this weekend. As for what works, normal templates and routing and Datastore usage works. Beaker has a "google" backend that uses Datastore, which has had intermittent problems so I'm not sure if it's working now. The problem with the interactive traceback seems to be due to the middleware disabling itself because of something in the runtime environment -- some situation that wasn't foreseen when the middleware was written. We just have to figure out what exactly that is and patch the middleware to work with App Engine. "paster controller" and "paster restcontroller" don't work with appengine-homedir because the configuration deletes the egg-info directory that contains the controller entry point. I'm going to see if the directory can be retained in that structure, and if that'll be enough for the commands to work. "paster create" and the others work because they're built into Paste. As for Windows-specific problems, I don't know of any Pylons/App Engine developer who uses Windows, so we'd need a Windows-using developer to troubleshoot those. You know of any (hint)? It's the same problem with Virtualenv: the Windows users haven't been giving feedback or patches. -- Mike Orr <[email protected]> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
