On Sat, Oct 24, 2009 at 7:58 PM, Jason S. <jas...@tuffmail.com> wrote:
> > This is a major rework of my GAE/Pylons article, which requires fewer > steps now. There's no Paste patch, and it still uses a regular INI > Better and better. The more I think about it, the more I would *prefer* to run in the appserver. There are just so many little weirdnesses, that I'd be afraid of things working well for 4 months, then suddenly crashing with a 500 error when I push an update. *BUT* and this is a big one, I really need the debugger. To try and make sense of the cgi tracebacks is harsh. Does your setup here support that? I'm also getting frustrated with the speed. GAE is warning me that my pages are taking too much cpu, and may blow my quota (I don't even have any users yet; just testing things). And this is for a page with almost nothing... just grab a record set, iterate through it and dump a one-line <p> into a mako page. So, maybe it's because Mako isn't caching? How has your experience been actually running your tests? I would imagine that some of the Pylons stack can be turned off in favor of lower-level GAE stuff (static files, for example). And there is caching via beaker. But at some point, if it takes me 10x as long to write an app for GAE vs. for a Linode install, I feel like a chump. --~--~---------~--~----~------------~-------~--~----~ 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 pylons-discuss+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
