Choosing a Python framework for web development?
nostrademons: Start with Django unless you have a very good reason to use one of the other ones.  Very good reasons include1.) Previous skills with Mako, SQLAlchemy, Paste, or any of the other libraries that Pylons or Turbogears is based upon.2.) Previous code in one of the above libraries3.) Functionality needs that Django cannot satisfy in at least a couple of the following areas: authentication, user models, multiple database support, template extensibility, deployment.  I say "at least a couple" because if you just need one, you can import it like you would in any other framework.  The price is that many existing Django add-ons won't be aware of your choice.Bad reasons include:1.) "Django's only for CMSes."  Not true; it works just as well for anything that involves web apps, including AJAX apps.2.) "It's not scalable enough."  The Washington Post runs on Django; I doubt you're going to get more pageviews than them.3.) "My data doesn't easily fit in the relational paradigm."  That's what the import statement is for; you can hook any data source you want up to a Django view.4.) "Django's templating language is too restrictive."  That's what template tags are for.5.) "I'm really doing a full-fledged AJAX app, not a website."  You can output JSON or XML data from a Django view as easily as HTML, and you're not limited to any particular JavaScript library.  (I actually think Django views are more convenient for this than Pylons controllers; there's less boilerplate.)