The answer is really whatever you're most comfortable with. The usage of the App Engine services is more or less that same regardless of framework (with some notable differences for django). Since you mentioned you're new to webdev with python - Django can be very intimidating. Webapp2 is a microframework and is app engine native so it'll be really easy to get started with that. Flask <http://flask.pocoo.org/> is also a great and popular choice.
At Cloud Sherpas, we built Ferris 2 <http://ferrisframework.org/> on top of webapp2 and the app engine services specifically for developing apps on Google App Engine. Our motivation was to reduce the amount of time we spent writing the same code over and over. Both ourselves and open-source users have used it in tons of apps big and small over the last 3 years. It's a traditional MVC framework (similar to Rails or Django) so it can be quickly picked up by anyone familiar with those concepts. If learning an entirely big new framework isn't something that sounds fun to you, I agree, which is why for Ferris 3 we've added the ability to use the tools with any framework - such as Webapp2, Flask, or Django. These tools include helpers for datastore, caching, google apis, etc. Ferris 3 is currently in alpha and you can read more about that here <http://blog.jonparrott.com/ferris-3-alpha-release/> and checkout the code here <https://github.com/jonparrott/ferris3> (also here's the flask example <https://github.com/jonparrott/flask-ferris-example>). On Monday, October 13, 2014 2:07:28 PM UTC-4, Todd Thomas wrote: > > Hey guys, I attended a local Python User Group meeting last week; the > presentation on GAE was great; during which we walked through an example of > pushing a local/dev Django app to GAE - brilliant. > > Now that I'm inspired I'd like to dive in. I use Python to manage the > Linux OS but I'm a total newb with web dev so I have questions. > > Assumptions: > > 1. All aspects will be kept open; ie: HTML5, CSS, JavaScript, Python > 2. The project will be started from scratch. > 3. A an interest in *an "As Pure As Possible" App Engine experience*. > These pieces have been identified to get started: > > > - App Engine <https://cloud.google.com/appengine/> (SDK) > - Google Web Starter Kit > <https://developers.google.com/web/starter-kit/> > - Jinja 2 <http://www.pocoo.org/projects/jinja2/> (templating) > - JavaScript: AngularJS <https://angularjs.org/> with the possible > inclusion of a Classy <http://www.pocoo.org/projects/classy/> backer. > - OAuth2 <http://oauth.net/2/> Integration (eventually) > - Vim > > Q: What is the best (supported, documented, *scalable*, most widely-used, > etc.) framework to use with GAE? > > Q: Why? > > Q: Are there some other pieces of this puzzle I might be missing? > > webapp2 <https://cloud.google.com/appengine/docs/python/tools/webapp2> is > highlighted on the GAE > Python > Tools age but Django gets special > mention <https://cloud.google.com/appengine/docs/python/tools/libraries27> as > well; still others are supported > <https://code.google.com/p/tipfy/wiki/AppEngineFrameworks>; it's very > confusing. > > I'm jazzed but research has become exhausting. I need to hear from the > battle tested souls out there; essentially, those who have already "stepped > in it". *Just a newb trying to get started on the right foot.* > > Thanks in advance guys, > TT > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout.
