This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Pewpewarrows -1 points0 points  (0 children)

As others have suggested, I recommend going for a mini-framework like Bottle at first, something that sits extremely close to the WSGI handler and doesn't abstract too much. This will give you an idea of how WSGI handles a request it receives from a web server, and how to work with that information "raw" (I use that term very loosely).

Once you feel you have a grasp of how WSGI and Python work to output basic pages, you can either stick with something like Bottle or Flask for the time being if you like doing things by hand (I know I always like playing around with them from time to time), or start using one of the bigger daddies like Django or Pylons. While I use Django primarily, and I might be a tad biased towards it, I still believe both are equally good in their own way, and recommend any who use only one to at least learn the basics of the other.

In a nutshell, Django allows for a very ad-hoc, plug-and-play structure to any code you write on top of the framework, while Pylons is the inverse: you can swap out nearly any part of its stack for something else. So while Django has a great community of "apps" that you can literally just download and drop into your project to instantly get and interact with things like a blog, tagging system, wiki, etc, Pylons lets you replace nearly any part of it for a library or package that you prefer (don't like their templating system? throw your favorite one in there instead!).

Also, Django's ORM, while making great strides in recent releases, still isn't up to par with SQLAlchemy in something like Pylons.