FunkLoad 1.3.0 and 1.3.1 (which fixed a bug in the previous release) are
FunkLoad 1.3.0 introduces a new http-proxy based recorder for user
sessions. It also fixes a couple of outstanding bugs.
Grab FunkLoad 1.3.1 on: http://funkload.nuxeo.org/
FunkLoad is a open source functional and load web tester, written in
Python, whose main use cases are functional and regression testing of
web projects, performance testing by loading the web application and
monitoring your servers, load testing to expose bugs that do not surface
in cursory testing, and stress testing to overwhelm the web application
resources and test the application recoverability, and writing web
agents by scripting any web repetitive task, like checking if a site is
We're pleased to announce the release of Wing IDE for Python 2.0.4.
This is a bugfix release and is a free upgrade for Wing IDE 2.0
users. The release can be downloaded from:
Highlights of this release include:
* Preference for syntax highlighting colors in Python, C/C++,
and Java files
* Support for Zope 2.8 and gtk 2.8
* Modest improvements in search performance
* Template panel is part of default tool set (Wing Pro only)
* Over 40 bug fixes
This release is available for Windows, Linux, and Mac OS X, and
can be compiled from sources on *BSD, Solaris, and other Posix
A complete list of changes is available here:
For more information see:
Product Info: http://wingware.com/products
The Wingware Team
Flightdeck-UI Online version 0.3.91 has been released. This is a
minor update to the advanced beta version (0.3.9). Here is the list
of changes in the new release.
* A bug that caused the analog clock in the demo panel
to read incorrectly after Daylight Savings Time ends
has been fixed.
* A special offset class ("FdUI.logic.Offsets.Localtime")
has been added, which automatically adjusts to Daylight
Savings Time without the need to restart the panel daemon.
The "Offsets" module itself is also new.
* The wind speed label in the weather demo panel was
too narrow, causing the digital wind display to be cut
off in some cases. This has been fixed.
The distribution includes detailed installation instructions and two
example control panels. The installation is designed to be a very
simple process -- please contact the author if you have questions.
See the homepage:
or download directly from:
What is Flightdeck-UI
The goal of the Flightdeck-UI project is to apply ideas from aircraft
instrumentation design to general purpose user interfaces.
The new web service version (Flightdeck-UI Online) retains the plug-in
architecture of previous releases. Each plugin, however, may now be
monitored at different sampling rates. Multiple data sources (hosts
on the Internet, embedded devices, etc.) can be tracked
Also, virtually any Unix command that you enter from the shell can be
automatically executed by Flightdeck-UI Online, and the results
displayed by the system's virtual instruments.
Although the web service requires a Flash front end (developed using
only the MTASC open source ActionScript compiler; see
http://www.mtasc.org/) Flightdeck-UI Online is still primarily written
The author welcomes any ideas and suggestions: please email them directly
I'd like to announce "seppo" - simple embarrassingly parallel python.
This should be considered a very alpha version, and was released to the
public to gauge interest/reaction.
The map function is well-known in Python, allowing a single function to
be called on each member of an iterable sequence:
map( function, [1,2,3,4] )
The seppo module allows the same functionality, but distributed over
seppo.map_parallel( some_module.function, [1,2,3,4] )
In this case, each iteration may evaluate the function in a different
process, possibly in a different computer. The idea is a simple concept
and is hopefully natural transition for Python programmers to use the
power of multi-processor computers and clusters.
For more information, or to download
Please see: http://www.its.caltech.edu/~astraw/seppo.html
FYI. (This is not Python-specific per-se, but everyone I know using
Python has adopted docutils and rest, so this will be of interest to
most people on this list using emacs.)
emacs support for reStructuredText has been greatly improved and
rewritten over the past few weeks. All emacs files have now been
grouped in a single package, rst.el, with lots of new features.
All the juicy details can be found here:
rst.el is part of the docutils repository:
Note that all the old rest emacs packages (restructuredtext.el,
rst-mode.el, rst-html.el) are obsoleted by this new package-- the new
package contains all their functionality and more. Delete your old
Some tools for Subversion that might be useful for others.
Replicates the directory structure and files of <src> into <dest>,
performing the necessary additions and deletions to register the
changes files in <dest> into Subversion. <dest> is assumed to be a
Subversion checkout. Files that exist on both sides are diffed to
figure out if there are changes to be copied.
Take a list of directories, each representing a version of some
files (like a checkout of a release of some software), and imports
each of these sequentially over an existing checkout, registering the
new fileset and creating a subversion release for every directory
Indra is a set of simple programming interfaces that were defined with
the intention of isolating web application code from specific
back-ends. The goal is to be able to write powerful web applications
with a clear separation that allows easily retargeting an application
to a different backend, without having to rewrite the application
When I wrote these interfaces, I was writing my own web application
framework, and I worried about writing code that could not be
retargeted to another platform in the future. What I decided to do was
formalize what the interface between my application's code and the web
app framework. To this effect, I had to identify what were the core
components that I was using and came up with this set of interfaces.
I have since implemented a web framework that implements all the
interfaces provides by Indra. The interfaces are relatively low-level,
and it would be easy to implement the same set of interfaces on other
(Since I thought this might be useful to others, I decided to share
it. Here it is.)
This is a revised announcement for tonight's Fredericksburg ZPUG
meeting. Andrew Sawyers is postponing his Squid and Zope
presentation until the January ZPUG meeting (January 11, 2006). This
is the new agenda:
Please join us November 9, 7:30-9:00 PM, for the sixth meeting of the
Fredericksburg, VA Zope and Python User Group ("ZPUG"). Using Zope
for newspaper publishing! The dangers of object oriented inheritance!
* Allen Schmidt, Sr. Programmer for Fredericksburg.com - the
website for the Free Lance-Star - will present on "Using Zope for
* Jim Fulton, CTO of Zope Corporation, will present an
abbreviated version of the argument given in Clemens Szyperski's
Component Software for why both inheritance and delegation (e.g.
acquisition) cause tight coupling and therefore should be avoided
except in special circumstances.
* We will serve delicious fruit, cheese, and soft drinks.
PyCon 2006 Call for Tutorials
Enjoy teaching classes or tutorials? PyCon 2006 is looking for
proposals for a pre-conference tutorials day. PyCon 2006 will be held
February 24-26 in Addison, Texas (near Dallas). Tutorials will be held
on February 23, at the same location.
Tutorial sessions will be a half day (3 hours, with a 15-minute break);
presenters may request two sessions in order to make up a full day.
Tutorials may be on any topic, but obviously should be instructional in
nature. Providing take-home materials for attendees is encouraged, and
tutorial presenters will receive $50 per student registered for theirsession (with a minimum payment of $500, and a maximum of $1500).
Extra consideration will be given to presenters with prior experience
teaching classes or giving conference tutorials. Please provide one
reference or evidence of such prior experience (sessions taught at
OSCON, EuroPython, local user groups, etc.).
PyCon attendees will register for tutorials. We reserve the right to
cancel tutorials with low attendance; presenters will not be paid for
Example tutorial topics can be found at:
* Submission deadline: November 15, 2005
* Acceptance deadline: November 22, 2005
* Cancellation date: January 15, 2006 (for inadequate attendance)
Proposals should be 250 to 1000 words long (i.e., one to four pages in
manuscript format), containing the following information:
* Author name(s)
* Contact Information
* (Recommended) At least one previous presentation/teaching engagement
* Summary of proposed presentation
* Presentation outline
* Intended audience (non-programmers, beginning programmers, advanced
users, CPython developers, etc.)
E-mail your proposal to <pycon(a)python.org>.
ASCII format is preferred (plain or reST), with HTML as a secondary
alternative. If you have any questions about submission, please send
mail to the conference organizers at pycon(a)python.org.