wheezy web: introduction

The key of success for any medium to high complexity system is in separation of domain concerns. Given that choice in architectural design for web framework, the development activities are split by distinct, non-dependent parts. The wheezy.web is a lightweight WSGI web framework and serves a glue purpose between various other packages developed under wheezy.* umbrella in loosely coupled way, it combines things essential for web application developer (presentation slides are here):

• routing - simple extensible mapping between URL patterns (as plain simple strings, curly expressions or regular expressions) to a handler; the mapping can include other mappings and constructed dynamically; reverse path by name
• domain model update from request input; validation
• transparent validation errors integration in HTML widgets
• authentication/authorization
• i18n (gettext)
• middlewares, response transforms, cookies, etc
• content caching, HTTP cache policy and cache profiles + cache dependency
• functional testing
• template engine agnostic, however brings wheezy.template. It offers HTML widgets for various template engines to make your code more readable and consistent (via template preprocessing to generate an optimal markup for given template engine)
• integration with pycrypto, lxml, python-memcached and pylibmc; the wheezy.captcha library is based on PIL
• documentation per package, tutorial, examples, demo
• Python 2.4 - 3.3+ ready

wheezy.web framework is high quality software with special attention paid to performance, concurrency and efficiency - key characteristics for modern web endeavors. It conforms to PEP8 standard and comes with high test coverage, automated build for various python versions which form a solid foundation that is easy to maintain.

Features, you find in other frameworks, but not here:

• web sessions: it is recommended to use fine grained caching instead, same development effort with better outcome. Take this thought: I have application with 20 handlers, each store some unique data, but only one handler serves an incoming request, so I need just data unique to my handler. With session, you receive all data, stored by various handlers... your handler done... all session data are stored back. How things go in concurrent attempts to `modify` the same session, e.g. ajax calls? It is not a problem for something small, in-memory,... but that is a huge problem as you scale and go big
• gzip middleware: nginx do that better
• static site caching middleware: nginx+uwsgi do that better
• model update, validation and HTML widgets as a single `Form Library`: you will not find it here. All three are separate actors, mixing them all-in-one loose flexibility
• ORM: `separation of concerns` tells me it distinct feature that has very little to do with web... integration is usually few lines of code regardless of web framework
• Admin: the bloat of code can be so killing that you even don't realize where web framework ends and where mess starts. In my opinion it is distinct feature, and should evolve alone

Attention to efficiency of design is one of well distinguished key principals of wheezy.web framework. If you think there is a `cool feature` and it is missing, just go ahead and propose to add it.

What I am looking for? The python community feedback and tight collaboration.