About

PyWF inherits features of Werkzeug and adds one more abstraction level.

• provides centralised project settings storage.
• provides project debugging (uses Werkzeug-debugger).
• provides separate project functionality through applications.
• provides simple integration with Jinja2 and SQLAlchemy.
• provides project internalization/localization.
• flexible, provides extensions.

PyWF uses Werkzeug as WSGI stack and opster as command line parsing tool, all other components are optional.

Changes

Previsions branch(0.1.x) is stalled, because all components (even optional) integrated in the core, also core did not support extensions.

Next branch did redesigned with extensions support, all optional components moved from core (same as jinja2, sqlalchemy) and now available as extensions. It is major change, branch version incremented to 0.5.x

Then many components are redesigned (backward incompatible) and new branch (0.6.x) started.

Currently project in development, no have stable version, but usable.

Core components

• Werkzeug - WSGI stack
• opster - Command line parsing tool

Extensions

• pywf.ext.debug - allow application debugging, uses werkzeug internal debugger
• pywf.ext.server - allow run internal developer server or flup, fapws if avaliable
• pywf.ext.file_session - allow unsing sessions stored in files
• pywf.ext.jinja - integration with Jinja2 Template engine (Jinja2 package required)
• pywf.ext.sqlalchemy - integration with SQLAlchemy - database stack (SQLAlchemy package required)
• pywf.ext.gettext - allow internalization uses gettext

Development version

sudo easy_install PyWF==dev

Resources

• Source.
• Online development documentation.