4 ms·
Yes. It is stressful. Look for libraries that make working with WSGI as painless as possible. Working with WSGI directly allows you to write modular code that
by enduser 16y ago
Yes.
It is stressful.
Look for libraries that make working with WSGI as painless as possible. Working with WSGI directly allows you to write modular code that works together gracefully with other WSGI code. Pylons is really just an amalgamation of WSGI modules. Smart people can amalgamate their own modules.
Django was written before WSGI was an established standard. It has the advantages of being established, a relatively large pool of developers, and the admin interface. It has the disadvantage of dictating your project layout, not integrating well with other WSGI modules, and having a large degree of lock-in.
The best options are Flask (for a simple start), Pylons (for more obvious out of the box functionality), WebOb (for a simple and slightly too magical WSGI library), and Werkzeug (for a well-written library that dictates nothing).
- lowkey 16y agoUm, what about Web2Py? I must say, so far I've been extremely impressed. It's polished, has batteries included, is very similar to Ruby on Rails in experience, and even has a built-in web-based IDE. (http://www.web2py.com/ http://www.web2py.com/)
- joshu 16y agoi've seen it before but every time i saw the word "enterprise" my helmet snapped shut in self-defense.