#~ ANN: RuneBlade-Foundation-0.3.0 ~~~~~~~~~~~~~~~~~~~
RuneBlade Foundation is a set of GUI skinning and other tools created to ease
the development of XML-based applications. Application such as Jabber (XML)
for communications; XML "skin" for a wxPython GUI; or, an XML "skin" for
xhtml or svg output similar to other templating engines.
More information, including distributables, can be found at
http://www.runeblade.com/foundation/ or by contacting the author at
RuneBlade Foundation Release 0.3.0 includes:
Utilities for WeakBinding and ContextApply wrappers for callable
objects. XML Builder / XML Objectifier / XML Class Builder tools
for truly object oriented XML on pythonic terms.
An XML-based messaging system. See http://jabber.org
Event driven architecture based on Subject/Observer.
Collections of client or component connections are natively support.
Support for message sending, presence changes, and iq packets helpers.
Modules include presence maps, message routers, and standard iq responses.
Base framework for inheritable attributes, etc.
Python-in-xml skin implementation, for creating skins that are alive.
wxPython skin production implementation. (See http://wxpython.org)
DOT output. (See http://www.research.att.com/sw/tools/graphviz/)
xhtml/svg templated output.
Tools modeled after their classic namesake, helping to create an
event-based architecture. Used heavily by both the Skinning and
A bag O tricks for wxPython. (wxPython was the first skin,
and as such, gets all the attention...)
RuneBlade Foundation is governed by a BSD style open-source LICENSE, and can
be found at http://www.runeblade.com/foundation/bsd.html
Future announcements will also be made via mailing list, which can be found
- RuneBlade Foundation is a set of GUI skinning and other tools created to
ease the development of XML-based applications. (31-Jul-02)
Version 0.8 of the Python/XML distribution is now available. It
should be considered a beta release, and can be downloaded from
the following URLs:
Changes in this version, compared to 0.7.1:
* Python 1.5 is not supported anymore; Python 2.0 or higher
* Expat has been updated to 1.95.4.
* pyexpat is now always built.
* pyexpat now reports skipped entities.
* pyexpat now can combine subsequent character data events
into a single callback invocation; set the parser's
buffer_text attribute to true to enable this feature.
* pyexpat can now report namespace prefixes. Set the parser's
namespace_prefixes attribute to true to enable this feature.
* Various bugs in sgmlop have been fixed.
* Various DOM Level 3 symbolic constants have been added;
DOMStringSizeErr can now be spelled as DomstringSizeErr
again, and ValidationErr has been defined.
* Various DOM L1, L2 and L3 features have been added to
minidom: userdata, isSupported, getInterface, wholeText,
replaceWholeText, Entity, Notation
* minidom's .toxml now allows the caller to specify an encoding.
* The new module xml.dom.xmlbuilder implements the load part
of the DOM L3 Load/Store spec.
* The new module xml.dom.expatbuilder allows to create minidom
trees more efficiently, by using expat directly (rather than
using SAX). This is normally used via xml.dom.xmlbuilder.
* Bugs in c14n namespace processing have been fixed.
* Minor bugs in xmlproc have been fixed.
* xml.sax.expatreader now invokes resolveEntity properly.
* The sgmlop SAX driver now invokes skippedEntity.
* The xml-howto has been updated.
* Bugs in the MSIE, ADR, and NS XBEL parsers have been fixed.
The Python/XML distribution contains the basic tools required for
processing XML data using the Python programming language, assembled
into one easy-to-install package. The distribution includes parsers
and standard interfaces such as SAX and DOM, along with various other
The package currently contains:
* XML parsers: Pyexpat (Jack Jansen), xmlproc (Lars Marius
Garshol), sgmlop (Fredrik Lundh).
* SAX interface (Lars Marius Garshol)
* minidom DOM implementation (Paul Prescod, others)
* 4DOM and 4XPath from Fourthought (Uche Ogbuji, Mike Olson)
* Schema implementations: TREX (James Tauber)
* Various utility modules and functions (various people)
* Documentation and example programs (various people)
The code is being developed bazaar-style by contributors from the
Python XML Special Interest Group, so please send comments and
questions to <xml-sig(a)python.org>. Bug reports may be filed on
For more information about Python and XML, see:
Martin v. Löwis http://www.informatik.hu-berlin.de/~loewis
Version 0.4 of the scgi package is now available from:
The SCGI protocol is a replacement for the Common Gateway Interface
(CGI) protocol. It is a standard for applications to interface with
HTTP servers. It is similar to FastCGI but is designed to be easier to
Included in this package is mod_scgi, an Apache module that implements
the client side of the protocol. There is also a a Python package
called scgi which implements the server side of the protocol.
Changes in scgi 0.4
* Make debug() message a little more useful when we catch IOError on
* Fix a bug that caused the manager process to hang. The hang
was trigged when the maximum number of child processes were
running and one died while the manager was trying to find an idle
child to process a request.
Neil Schemenauer <nas(a)mems-exchange.org> | MEMS Exchange
Software Engineer | http://www.mems-exchange.org/
I've released version 1.3 of the Spread Module for Python:
About the Spread Module
This package contains a simple Python wrapper module for the Spread
toolkit (see below). The wrapper is compatible with Python 2.1 and
2.2. It wraps Spread mailboxes and messages in Python objects with
appropriate methods and attributes, and turns Spread errors into
Python exceptions. Virtually all Spread features are accessible from
>From the Spread website (http://www.spread.org):
Spread is a toolkit that provides a high performance messaging service
that is resilient to faults across external or internal networks.
Spread functions as a unified message bus for distributed
applications, and provides highly tuned application-level multicast
and group communication support. Spread services range from reliable
message passing to fully ordered messages with delivery guarantees,
even in case of computer failures and network partitions.
Spread is designed to encapsulate the challenging aspects of
asynchronous networks and enable the construction of scalable
distributed applications, allowing application builders to focus on
the differentiating components of their application.
Changes since release 1.2
- Critical bugfix: We didn't realize that the service_type argument to
Spread's SP_receive() is an input parameter as well as an output
parameter, and consequently didn't initialize it. Depending on what
trash happened to be sitting on the stack, this could cause Spread to
deliberately drop data (a backward compatibility feature in Spread
triggered by passing the DROP_RECV flag in service_type on input).
--Guido van Rossum (home page: http://www.python.org/~guido/)
SciParam 0.9.1 is a Python package to easily add additional quality
control for entering scientific parameters in wxPython-based user
See http://great-er.intevation.org/sciparam/ for download,
documentation and screenshots.
Copyright (C) 2002
Intevation GmbH <intevation(a)intevation.de>
Georgstraße 4, D-49074 Osnabrueck,
Thomas Koester <tkoester(a)intevation.de>
SciParam is released under the GNU General Public License.
Email: rufus(a)o-town.de (at work: tkoester(a)intevation.de)
leo.py 3.2 is now available at http://sourceforge.net/projects/leo/
This version fixes all known bugs, generalizes the @others directive
and improves the Import command.
The highlights of 3.2:
- Nested @others directives are now valid, an important improvement.
This simplifies files that define more than one class.
- Improved the Import command and squashed several bugs lurking there.
- Made the various Go commands in the Outline-Move/Select menu functional
by reassigning keyboard shortcuts.
- Fixed a crasher in the Prefs Panel.
- Fixed numerous bugs in the Set Colors command.
- Fixed syntax coloring of C strings that span multiple lines.
- The usual minor improvements and bug fixes.
leo.py requires Python 2.2 and tcl/tk 8.3 or above.
What is Leo?
- A programmer's editor, an outlining editor and a flexible browser.
- A literate programming tool, compatible with noweb and CWEB.
- A data organizer and project manager. Leo provides multiple views
of projects within a single outline.
- Fully scriptable using Python. Leo saves its files in XML format.
- Portable. leo.py is 100% pure Python.
- Open Software, distributed under the Python License.
Edward K. Ream email: edream(a)tds.net
Leo: Literate Editor with Outlines
German Python Board
A German Python Board for Python programmers..
The first german board for newbies and all the others! Check it out if
your language is German
Just started! Help to grow!
Carsten Sandtner (csandtner(a)web.de)
<a href="http://python.sandtner.net">German Python Board</a> -- A German
Python Board for Python programmers..
We're pleased to announce the release of CherryPy-0.4.
This release adds a new major feature that is very important
for high-traffic web sites: caching capability.
It also includes some compiler optimization.
CherryPy is a Python-based tool for developing dynamic websites. It
uses many powerful concepts together, which makes it unique in its
approach to website development.
CherryPy sits between an application server and a compiler. You write
source files, compile them with CherryPy and CherryPy generates an
executable containing everything to run the website (including an HTTP
Key properties/features of CherryPy are:
- Based exclusively on Python (runs everywhere Python runs)
- Delivers fast, robust, and scalable websites
- Developers can use OOP as well as AOP (Aspect Oriented
Programming) concepts to develop websites
- True separation of content and presentation
- Simple but powerful templating language
- "HTML editor safe" templating language (templates can go back and
forth between designers and developers)
- Powerful standard libraries to make your life easy
Other properties/features are:
- Can be linked to many databases (Oracle, Sybase, MySql,
- Can run behind another webserver (Apache, ...)
- Easy clustering and load-balancing set up for high-traffic
- Built-in caching capability
pyCGNS is a python wrapper on CGNS, the CFD General Notation System.
This is a specialized package for data representation and storage
for Computational Fluid Dynamics applications and tools.
This new pyCGNS release is up to date with CGNS v2.1 version.
Downloads, docs and extra stuff in
- a simple wrapper on top of ADF calls and MLL calls
- an attempt to an Object-oriented interface to CGNS mid-level lib
- all data arrays are Python Numeric Arrays
- tests and demos for ADF/CGNS
- some User's Guide to CGNS examples, a naca0012 sample, etc...
- a tree parser demo with an XML tree output, date stamps...
- tests on ADF, MLL and SIDS calls (not 100% coverage so far)
# v0.5 CHANGES:
- Change imports, now use a single one: import CGNS
- Stabilize path and node classes in SIDS (still experimental, see doc)
- Continue to wrap MLL (not tested)
- Update to new versions of CGNS/ADF and Python
- Update + automatize doc
- Correct some bugs, more testing
- Now use subversion (http://subversion.tigris.org)
Marc POINOT Alias: marcvs Email: poinot(a)onera.fr
ONERA -MFE/DSNA/ELSA Tel: 01.46.73.42.84 Info: elsa-info(a)onera.fr
29, Div. Leclerc Fax: 01.46.73.41.66 Site:
92322 Chatillon FRANCE Project: elsA Web: http://www.onera.fr
'mruclean' is a Python program which "cleans" selected MRU (Most Recently Used)
entries from the Win32 Registry. It is a useful demonstration of Python's
_winreg registry interface features. 'mruclean' can be found at:
# XX XX XX XXXXXX XX XX XXXX XX XX XXXX XX #
# XX XX XXXX XX XX XXX XX XX XXX XX XX X XX #
# XX XX XX XX XX XX XXXX XX XX XXXX XX XX XX #
# XX X XX XX XX XXXXX XX XXXX XX XX XXXX XX XX #
# XXXXXXX XXXXXX XX XX XX XXX XX XX XXX XX XXX XX #
# XXX XXX XX XX XX XX XX XX XX XX XX XX XX #
# XX XX XX XX XXX XX XX XX XXXX XX XX XXX X XX #
# THIS SOFTWARE MODIFIES YOUR WINDOWS REGISTRY AND CAN CORRUPT OR #
# OTHERWISE DAMAGE YOUR SYSTEM. DO ****NOT**** RUN THIS ON YOUR #
# SYSTEM UNLESS: #
# 1) YOU THOROUGHLY UNDERSTAND WHAT IS GOING ON IN #
# THIS PROGRAM. #
# 2) YOU HAVE VERIFIED THAT THE REGISTRY MODIFICATIONS IN #
# THIS PROGRAM ARE APPROPRIATE FOR ***YOUR*** SYSTEM #