Ask HN: Best Python Framework for Google App Engine? • Hacker News Board

Re: Ask HN: Best Python Framework for Google App Engine?

#11

Post by yanw » Thu, Jun 30, 2011, 10:46 PM UTC

Webapp2: http://webapp-improved.appspot.com/

Re: Ask HN: Best Python Framework for Google App Engine?

#12

Post by delsarto » Thu, Jun 30, 2011, 10:47 PM UTC

nixarn wrote: post #10

badragon wrote: post #7

Tipfy

Agreed. Tipy is awesome! http://www.tipfy.org/

Yes, but the documentation is a little out of date as the current version has changed significantly. Basically, don't go by anything you find on the web, make sure you use the docs/examples in the mercurial tree

Re: Ask HN: Best Python Framework for Google App Engine?

#13

Post by derwiki » Thu, Jun 30, 2011, 10:48 PM UTC

I like Bottle: http://bottlepy.org/docs/dev/

Re: Ask HN: Best Python Framework for Google App Engine?

#14

Post by skudervatchi » Thu, Jun 30, 2011, 10:57 PM UTC

best link to learn java

Re: Ask HN: Best Python Framework for Google App Engine?

#15

Post by ktarnowski » Thu, Jun 30, 2011, 11:00 PM UTC

Tornado is great as a standalone API/WWW server, but for WSGI-based environments, like Google App Engine, I would choose Flask (>= 0.7.1) over any other framework.

Flask, despite being a micro-framework, is extremely powerful. It's core is well-written and there's a lot of useful extensions out there (like Flask-WTF or Flask-Assets). Flask also works really well with Google App Engine (see example skeleton: https://github.com/kamalgill/flask-appengine-template; there's more on GitHub). With little effort you get WTForms and even Webassets support almost out of the box, in really elegant way.

Tornado will also do, since it's very similar to webapp and has very good templating system. However, since extensions ecosystem for Tornado is almost non-existent, one has to write more code to make up for it (e.g. integration with Webassets, management commands, OAuth support etc.).

There's also Tipfy, but I have absolutely no experience with it, so I can't vouch for it.

Re: Ask HN: Best Python Framework for Google App Engine?

#16

Post by jsdalton » Thu, Jun 30, 2011, 11:04 PM UTC

A nice alternative to the built-in webapp framework is webapp2: http://code.google.com/p/webapp-improved/

It's basically a superset of webapp with some great additions and tweaks.

Re: Ask HN: Best Python Framework for Google App Engine?

#17

Post by tghw » Thu, Jun 30, 2011, 11:32 PM UTC

kenneth_reitz wrote: post #2

Flask. Docs: http://flask.pocoo.org/

Seconded. We used the flask-appengine-template (https://github.com/kamalgill/flask-appengine-template) and it's been great so far.

Flask and Jinja2 make views and templates really easy, and the AppEngine data store fits well for the models.

Re: Ask HN: Best Python Framework for Google App Engine?

#18

Post by jbaker » Thu, Jun 30, 2011, 11:43 PM UTC

tghw wrote: post #17

kenneth_reitz wrote: post #2

Flask. Docs: http://flask.pocoo.org/

Seconded. We used the flask-appengine-template ( https://github.com/kamalgill/flask-appengine-template ) and it's been great so far. Flask and Jinja2 make views and templates really easy, and the AppEngine data store fits well for the models.

I will third and fourth Flask for App Engine. For me, it strikes exactly the right balance between light-weight, flexible, and powerful.

Re: Ask HN: Best Python Framework for Google App Engine?

#19

Post by cageface » Fri, Jul 01, 2011, 12:30 AM UTC

kenneth_reitz wrote: post #2

Flask. Docs: http://flask.pocoo.org/

Agreed. I'm more of a Rails/Sinatra guy but if I had to write something for app engine I'd definitely start with Flask.

Re: Ask HN: Best Python Framework for Google App Engine?

#20

Post by nmb » Fri, Jul 01, 2011, 12:31 AM UTC

badragon wrote: post #7

Tipfy

Tipfy is nice, but its documentation is horribly out-of-date. The last time I tried using it, I had to dive into the source code several times to figure out what was going on. Eventually I ended up moving off of app engine. (I considered contributing to the docs, but I would have had to spend a lot of time learning the codebase as parts of it had been heavily restructured since the docs were last updated.)