License

Uliweb is released under BSD license.

Features

Organization

MVT(Model View Template) development model.

Distributed development but unified management. Uliweb organizes a project with
small apps. Each app can have its own configuration file(settings.ini), template
directory, and static directory. Existing apps can be easily reused, but are treated as a compound.
web application project if configured as such. Developers can also
reference static files and templates between apps, thus easing inter-application data exchange.
All apps in a project are loaded by default if INSTALLED_APPS is not configured in
the configuration file. All separate app configuration files are automatically processed at
project startup.

URL Mapping

Flexiable and powerful URL mapping. Uliweb uses werkzeug’s routing module.
User can easily define a URL, which in turn can be easily bound with a view function.
URLs can also be created reversely according to the view function name. It supports
argument definitions in URLs and default URL mapping to a
view function.

View and Template

View templates can be automatically applied. If you return a dict variable from
view function, Uliweb will automatically try to match and apply a template according
to the view function name.

Environment execution mode. Each view function will be run in an environment,
which eliminates the need to write many import statements. Plus there are already many
objects that can be used directly, for example: request, response, etc. This is DRY and saves a lot of coding

Developers can directly use Python code in a template, the Python code does not neede to be indented
as long as a pass statement is added at the end of each code block.
Uliweb also supports child template inclusion and inheritance.

ORM

Uliorm is based on SQLAlchemy package, so you can use Model layer and SQL
expression layer both.

Uliorm integrates with alembic package, you can use it to migirate database
automatically.

Provides a command line tool that developers can use to extract .po files.
This can happen either at the app level or project level process. It can automatically merge .pot files to existing
.po files.

Extension

Dispatch extension. This is a dispatch processing mechanism that utilizes different
types of dispatch points. So you can write procedures to carry out
special processes and bind them to these dispatch points. For example, database
initicalization, I18n process initialization, etc.

middleware extension. It’s similar to Djangos. You can configure it in configuration
files. Each middleware can process the request and response objets.

Special function calls in the views module initial process. If you write a special
function named __begin__, it’ll be processed before any view function can be processed,
this allows developers to do some module level processing at that point, for example:
check the user authentication, etc.