- Linux, Windows
- Python versions
- Python 2.5 and above
Wasp works in three modes. In client mode Wasp requires no deployment platform but compiles templates in batch mode. In CGI mode it works with an appropriate web server. In server mode it runs embedded in its own threaded web server.
Suitable for those who wish the conventional URL/file website paradigm. Not (as) suitable if you wish to code your entire site in an OOP fashion with virtual files. Not WSGI compatible.
Python code may be freely added as plugins with no special dependencies or restrictions. Code may also be inserted into page templates. A streamlined web environment is provided with easy access to CGI info, cookies, sessions, etc.
Wasp can access any Python modules, stored in shared or restricted locations. There are no limitations on how the designer partitions business logic from other components.
Session, Identification and Authentication
None provided, so you can use your favourite. Wasp is database agnostic.
Wasp contains a simple templating system that allows Python code in template files if you so wish.
Wasp was developed when there were relatively few alternatives for Rapid Application Development in Python for the web. Now there are many such. Wasp distinguishes itself in its maturity (in development since 2001), currency (new version provides significant improvements), simplicity (installs easily with no dependencies), adherence to standard web paradigms (files are still files, URLs are still URLs), ability to run in command-line mode (no web server required to get the benefits of templating), remote debugging (really a life-saver), and thorough documentation.
Wasp may not be appropriate for high-traffic sites. Here the CGI mode might be a limiting factor, and the embedded web server mode is not (as of yet) sufficiently tested under duress to recommend.
Any Apache setup with Python 2.5