[ANN]Uliweb 0.0.1a1 released!
limodou at gmail.com
Fri Oct 2 15:37:51 CEST 2009
:Author: Limodou <limodou at gmail.com>
Uliweb is a relatively new Python based web framework. Before I
started to create
this framework,I had used a few other frameworks such as Karrigell, Cherrypy,
Django and web2py, but they did not satisfy my needs due to several
reasons. I then decided
to create a web framework that combined the strengths of these
frameworks, keeping in mind
that the main focus is to make Uliweb easy to use yet powerful.
This project was created and lead by Limodou <limodou at gmail.com>. It
is in constant development
from several other developers around the world.
Uliweb is released under GPL v2 license.
Uliweb was not created totally from scratch. It uses some modules created by
other developers, for example:
* `Werkzeug <http://werkzeug.pocoo.org/>`_ Used to handle core
processes in the framework.
For example: command line tools , URL Mapping, Debug, etc.
* `SqlAlchemy <http://www.sqlalchemy.org>`_ The ORM based on it.
Developers can access
databases, or use the module separately.
I also referenced some code from other web frameworks, for example:
* The Templating system is styled after the one used in `web2py
improvements were made.
I also constructed a few new "wheels" myself. For example:
* Form processing module. Developers can use it to create HTML code,
validate submitted data and
convert submitted data to Python data types.
* I18n processing including template support, language lazy process.
* Uliorm, which is an ORM module, was built on top of SqlAlchemy. I
also referenced from
GAE datastore module.
* Framework runtime process.
* Plugin mechanism, styled after the one used in the `UliPad
* MVT(Model View Template) development model.
* Distributed development but unified management. Uliweb organizes a
small apps. Each app can have its own configuration
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
* 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 and Template
* View templates can be automatically applied. If you return a dict
view function, Uliweb will automatically try to match and apply a
to the view function name.
* Environment execution mode. Each view function will be run in an
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.
* Uliorm is the default ORM module but not configured by default.
Developers are free to use any
ORM module as preferred.
* Uliorm supports model creation and automatic database
and table structure modification).
* Can be used in python and template files.
* Browser language and cookie settings are supported including
automatic language switching.
* 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
* Dispatch extension. This is a dispatch processing mechanism that
types of dispatch points. So you can write procedures to carry out
special processes and bind them to these dispatch points. For
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.
* Command Line Tools
* Export a clean working environment to an assigned directory.
* Create app, and include the basic essential directory structure,
files and code.
* Export static files, you can export all available apps' static files to a
* Startup a development web server thats supports debugging and autoreload.
* Several project and app management tools.
* Supports easy deployment on the GAE platform.
* Supports mod_wsgi, cgi, fast_cgi, scgi.
* Provide a development server, and can be automatically reload when some
module files are modified.
* Enhanced debugging, you can check the error traceback, template
debugging is also supported.
* Various demos are available for anyone interested in learning more
It includes all core codes and also all source code of
`uliwebproject <http://uliwebproject.appspot.com>`_ ,
and some other demo codes, which can be used directly/freely as you wish.
* Uliweb supports static file access directly, and it can also process
* Simple and easy to use web framework.
* The web framework should be flexiable and easy to extend.
* The web framework should be able to be deployed in different platforms.
* Provision of enough sample code.
* Provision of concise and easy to understand documentation.
I like python!
UliPad <<The Python Editor>>: http://code.google.com/p/ulipad/
UliWeb <<simple web framework>>: http://uliwebproject.appspot.com
My Blog: http://hi.baidu.com/limodou
More information about the Python-announce-list