Webware for Python version 1.1 released on 08/03/11
Changes
- The main change in the Webware 1.1 branch is that it now requires
at least Python version 2.4, while the Webware 1.0 branch still supports
old Python releases down to version 2.0. This move allowed us to get rid
of a lot of cruft, workarounds and old fashioned code; the code has become
much cleaner and leaner, and by using more modern Python idioms also faster
in many places. We do not yet support Python 3, but these changes give us
a good starting point for further modernization of Webware for Python.
- We also changed our style guideline and are using 4 spaces instead of
tabs throughout our codebase now, in order to conform a bit more with PEP8.
We did not modernize our naming conventions, though, because we want to stay
backward compatible with existing Webware applications.
- The methods and objects which have been marked as deprecated
in version 1.0 and modules that are now available in the standard library
have been removed in Webware for Python 1.1.
- The
NamedValueAccess "magic" has been removed. See the
MiscUtils release notes for details.
- We are now only using new-style classes in our code base. The
Object root class for WebKit objects has gone.
- Webware (particularly MiddleKit) does not support
mxDateTime
types any more, only the native datetime types. However, if python-dateutil
is not installed, Webware will still use mxDateTime internally
for string parsing (but the results will be datetime anyway).
This makes datetime handling much clearer and easier maintainable.
New Features
- Added an adapter for any WSGI compliant webserver to communicate with
the Webware application server, which you can use straight away as WSGI
application script file for mod_wsgi.
- Added new session store classes based on shelve and Memcached.
- MiddleKit now supports SQLite as database.
- A mod_webkit binary for Apache 2 64bit on Windows is now included.
Fixes
- Fixed a long outstanding issue with filenames in tracebacks: Since the
installer compiled the files from a different directory (Webware) than the
appserver uses (WebKit), the stored filenames (co_filename) could sometimes
not be resolved.
- Fixed problems when shutting down an app server with hanging threads.
- More WebKit bugfixes are listed in the WebKit release notes.