Mailman 3 May 2003 - Python-announce-list

Flightdeck-UI MVM and Library 0.2.0 (Stable) Released
by fdui＠openlight.com May 27, 2003

May 27, 2003

This is a stable (production) release of the Flightdeck-UI library and Multi-Variable Monitor (MVM). Downloads are available from the project homepage ("http://www.openlight.com/fdui/"). The screenshots are here: "http://www.openlight.com/fdui/screens.html". The goal of the Flightdeck-UI project is to apply ideas from aircraft instrumentation design to general purpose user interfaces. The project consists of a library (which provides widgets based on the basic instruments of flight) and the Multi-Level Monitor (MVM) monitoring application. MVM can be quickly configured to track data from several sources (for example free disk space on your machine, the local weather, the number of visits to your website, etc.). It will then sit in some corner of your desktop, allowing you to read this information with an occasional glance. MVM includes a graphical editor and theme support. Support for multiple concurrency models in MVM plug-ins has been added in this release (asynchronous I/O and thread pool examples are included in the distribution). In addition, it is now easier to write simple plug-in modules, with functions that return integer or floating point numbers. For more information, see the README-MVM.TXT file ("http://www.openlight.com/fdui/README-MVM.TXT"). A number of bugfixes (particularly in the graphical editor) as well as enhanced error notification have also been added. Some of the new plug-ins (most notably the ones using thread pools) perform a clean shutdown when you exit MVM. If your Internet connection is hung up, you might have to wait a little for the I/O to time out so that the threads can stop (it is not possible to interrupt a Python thread). MVM and the Flightdeck-UI library are both open source/free software. They have been tested under Linux (RedHat 7.2) and under Windows 95. Questions can be emailed to originator of this message. Your ideas and participation will be appreciated!

1 0

Next meeting: Tuesday night
by Peter Hansen May 26, 2003

May 26, 2003

The Python user's group for the Greater Toronto Area will meet at the usual location (519 Church St.) on Tuesday, May 27, from 8 to 10 pm. Details are here: http://web.engcorp.com/pygta/wiki/NextMeeting I'm planning an informal presentation about a new tool we've developed at Kaval, which is a Python-based testing framework for Javascript in Internet Explorer on Windows. The combination of Python tools involved includes: - PyUnit (aka standard module unittest, for the tests) - win32com (Mark Hammond's amazing library, for ActiveX control of IE) - Twisted (for serving test pages locally) In a nutshell, tests are written in Python in the usual manner, but the code under test executes within IE, served up from localhost, under ActiveX control. -Peter

1 0

ANN: managesieve 0.2
by Hartmut Goebel May 26, 2003

May 26, 2003

Announcing: managesieve ============= Version 0.2 A MANGAGESIEVE client library for remotely managing Sieve scripts, including an interactive 'sieveshell'. This module allows accessing a Sieve-Server for managing Sieve scripts there. For more information about the MANAGESIEVE protocol see draft http://www.ietf.org/internet-drafts/draft-martin-managesieve-04.txt . What is MANAGESIEVE? -------------------- Sieve scripts allow users to filter incoming email. Message stores are commonly sealed servers so users cannot log into them, yet users must be able to update their scripts on them. This module implements a protocol "managesieve" for securely managing Sieve scripts on a remote server. This protocol allows a user to have multiple scripts, and also alerts a user to syntactically flawed scripts. This an interim measure as it is hoped that eventually Sieve scripts will be stored on ACAP. Availablity ----------- 'managesieve' is available for download at http://www.crazy-compilers.com/py-lib/#managesieve Requirements ------------ Requires Python >= 2.0 Not yet implemented ------------------- - Only athentication method LOGIN is currently supported. - STARTTLS is not yet implemented. - sieve-names are only quoted dump (put into quotes, but no escapes yet). Copyright/License ----------------- (C) Copyright 2003 by Hartmut Goebel <h.goebel(a)crazy-compilers.com> License: Python Software Foundation License http://www.opensource.org/licenses/PythonSoftFoundation.html License for 'sieveshell' and test suite: GPL http://www.opensource.org/licenses/gpl-license.php Credits ------- Based on Sieve.py from Ulrich Eck <ueck(a)net-labs.de> which is part of of 'ImapClient' (see http://www.zope.org/Members/jack-e/ImapClient), a Zope product. Some ideas taken from imaplib written by Piers Lauder <piers(a)cs.su.oz.au> et al.

1 0

OOPServer 0.2 Released
by Thomas Guettler May 25, 2003

May 25, 2003

This is the 0.2 release of OOPServer. It is a 100% Python solution for developing customised document management systems. It uses Zope as web application server. It includes an Upload-Client for integrating office or other software installed at the client. Up to now the target group are developers. Changes: OOPEmail is an email archive with full-text search, search for email adresses and display of *discussion threads* You can get the source from: http://guettli.sourceforge.net A demo is available: http://guettli.dyndns.org:8080 Thank you very much, to all who provided feedback to the last release! Thomas Guettler -- Thomas Guettler <guettli(a)thomas-guettler.de> http://www.thomas-guettler.de

1 0

msnp.py: MSN messaging in Python
by manish.j＠gmx.net May 24, 2003

May 24, 2003

http://msnp.sourceforge.net/ msnp.py is an implementation of the latest MSN Messenger protocol (currently, version 7) in object-oriented Python. Current Release: v0.2 v0.2 Features * Login; logout * Presence states (online, away, etc.) * Syncing of friend lists * Chat conversations (start, join, leave) * Instant messages * Typing notifications * HTTP proxy (tunnelling) support -- Manish Jethani (manish.j at gmx.net) phone (work) +91-80-51073488

1 0

ANN: managesieve 0.2
by Hartmut Goebel May 24, 2003

May 24, 2003

Announcing: managesieve ============= Version 0.2 A MANGAGESIEVE client library for remotely managing Sieve scripts, including an interactive 'sieveshell'. This module allows accessing a Sieve-Server for managing Sieve scripts there. For more information about the MANAGESIEVE protocol see draft http://www.ietf.org/internet-drafts/draft-martin-managesieve-04.txt . What is MANAGESIEVE? -------------------- Sieve scripts allow users to filter incoming email. Message stores are commonly sealed servers so users cannot log into them, yet users must be able to update their scripts on them. This module implements a protocol "managesieve" for securely managing Sieve scripts on a remote server. This protocol allows a user to have multiple scripts, and also alerts a user to syntactically flawed scripts. This an interim measure as it is hoped that eventually Sieve scripts will be stored on ACAP. Availablity ----------- 'managesieve' is available for download at http://www.crazy-compilers.com/py-lib/managesieve.html Requirements ------------ Requires Python >= 2.0 Not yet implemented ------------------- - Only athentication method LOGIN is currently supported. - STARTTLS is not yet implemented. - sieve-names are only quoted dump (put into quotes, but no escapes yet). Copyright/License ----------------- (C) Copyright 2003 by Hartmut Goebel <h.goebel(a)crazy-compilers.com> License: Python Software Foundation License http://www.opensource.org/licenses/PythonSoftFoundation.html License for 'sieveshell' and test suite: GPL http://www.opensource.org/licenses/gpl-license.php Credits ------- Based on Sieve.py from Ulrich Eck <ueck(a)net-labs.de> which is part of of 'ImapClient' (see http://www.zope.org/Members/jack-e/ImapClient), a Zope product. Some ideas taken from imaplib written by Piers Lauder <piers(a)cs.su.oz.au> et al.

1 0

python-dev Summary for 2003-05-01 through 2003-05-15
by drifty＠bigfoot.com May 23, 2003

May 23, 2003

+++++++++++++++++++++++++++++++++++++++++++++++++++++ python-dev Summary for 2003-05-01 through 2003-05-15 +++++++++++++++++++++++++++++++++++++++++++++++++++++ This is a summary of traffic on the `python-dev mailing list`_ from May 1, 2003 through May 15, 2003. It is intended to inform the wider Python community of on-going developments on the list and to have an archived summary of each thread started on the list. To comment on anything mentioned here, just post to python-list(a)python.org or `comp.lang.python`_ with a subject line mentioning what you are discussing. All python-dev members are interested in seeing ideas discussed by the community, so don't hesitate to take a stance on something. And if all of this really interests you then get involved and join `python-dev`_! This is the seventeenth summary written by Brett Cannon (going to grad school, baby!). All summaries are archived at http://www.python.org/dev/summary/ . Please note that this summary is written using reStructuredText_ which can be found at http://docutils.sf.net/rst.html . Any unfamiliar punctuation is probably markup for reST_ (otherwise it is probably regular expression syntax or a typo =); you can safely ignore it, although I suggest learning reST; its simple and is accepted for `PEP markup`__. Also, because of the wonders of programs that like to reformat text, I cannot guarantee you will be able to run the text version of this summary through Docutils_ as-is unless it is from the original text file. __ http://www.python.org/peps/pep-0012.html The in-development version of the documentation for Python can be found at http://www.python.org/dev/doc/devel/ . To view files in the Python CVS online, go to http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/python/ . .. _python-dev: http://www.python.org/dev/ .. _python-dev mailing list: http://mail.python.org/mailman/listinfo/python-dev .. _comp.lang.python: http://groups.google.com/groups?q=comp.lang.python .. _Docutils: http://docutils.sf.net/ .. _reST: .. _reStructuredText: http://docutils.sf.net/rst.html .. contents:: .. _last summary: http://www.python.org/dev/summary/2003-04-16_2003-04-30.html ====================== Summary Announcements ====================== So, to help keep my sanity longer than my predecessors I am no longer going to link to individual modules in the stdlib nor to files in CVS. It sucks down a ton of time and at least Raymond Hettinger thinks it clutters the summaries. Along the lines of the look of the summaries, I am trying out a new layout for listing splinter threads. If you have a preference in comparison to the old style or new style speak up and let me know. ========================== `Dictionary sparseness`__ ========================== __ http://mail.python.org/pipermail/python-dev/2003-May/035295.html Splinter threads: `Where'd my memory go?`__ __ http://mail.python.org/pipermail/python-dev/2003-May/035340.html After all the work Raymond Hettinger did on dictionaries he suggested two possible methods on dictionaries that would allow the programmer to control how sparse (at what point a dictionary doubles its size in order to lower collisions) a dictionary should be. Both got shot down on the grounds that most people would not know how to properly use the methods and are more likely to shoot themselves in the foot than get any gain out of them. There was also a bunch of talk about the "old days" when computers were small and didn't measure the amount of RAM they had in megabytes unless they were supercomputers. But then the discussion changed to memory footprints. There was some mention of the extra output one can get from a special build (all listed in Misc/SpecialBuilds.txt) such as Py_DEBUG. But the issue at hand is that there int, float, and frameobject free lists which keep alive any and all created constant values (although the frameobject is bounded in size). This is why if you do ``range(2000000)`` you won't get the memory allocated for all of those integers back until you shut down the interpreter. This led to the suggestion of just doing away with the free lists. There would be a performance hit since numerical constants would have to be reallocated if they are constantly created deleted, and then created again. It was also suggested to limit the size of the free lists and basically chop off the tail if they grew too large. But it turns out that the memory is allocated in large blocks that are chopped up by intobject.c. Thus there is no way to just get rid of a few entries without taking out a whole block of objects. ================================= `__slots__ and default values`__ ================================= __ http://mail.python.org/pipermail/python-dev/2003-May/035575.html Ever initialized a variable in a class that uses __slots__? If you have you may have discovered that the variable becomes read-only:: class Parrot(object): __ slots__ = ["dead"] dead = True bought_bird = Parrot() bought_bird.dead = False That raises an AttributeError saying that 'dead' is read-only. This occurs because the class attribute "overrides the descriptor created by __slots__" and "now appears read-only because there is no instance dict" thanks to __slots__ suppressing the creation of one. But don't go using this trick! If you want read-only attributes use a property with its set function set to raise an exception. If you want to avoid this problem just do your initialization of attributes in the __init__ call. You can also include __dict__ in __slots__ and then your instances will have a fully functioning instance __dict__ (new in 2.3). The key thing to come away with this twofold. One is the resolution order of attribute lookup when __slots__ is used which class/type and then the instances __slots__ attributes only if the class/type hierarchy did not turn up a data descriptor. The other is that __slots__ is meant purely to cut down on memory usage, nothing more. Do not start abusing it with little tricks like the one mentioned above or Guido will pull it from the language. ========= Quickies ========= `Draft of dictnotes.txt`__ After all the work Raymond Hettinger did to try to speed up dictionaries, he wrote a text file documenting everything he tried and learned. .. __: http://mail.python.org/pipermail/python-dev/2003-May/035246.html `_socket efficiencies ideas`__ This thread was first covered in the `last summary`_. Guido discovered that the socket module used to special-case receiving a numeric address in order to skip any overhead in bother to resolve the IP address. It has been put back into the code. .. __: http://mail.python.org/pipermail/python-dev/2003-May/035248.html `Demos and Tools in binary distributions`__ Jack Jansen asked where other platform-specific binary distributions of Python put the Demo and Tools directories. The thread ended with the winning solution be putting them in /Applications/Python2.3/Extras/ so they are a level below the root directory to prevent newbies from getting overwhelmed by the code there since it is not all simple. .. __: http://mail.python.org/pipermail/python-dev/2003-May/035252.html `updated notes about building bsddb185 module`__ Splinter threads: - `bsddb185 module changes checked in`__ Someone wanted the bsddb185 module back. Initially it was suggested to build that module as bsddb if the new bsddb3 module could not be built (since that module currently gets named bsddb). The final outcome was that bsddb185 will get built under certain conditions and be named bsddb185. .. __: http://mail.python.org/pipermail/python-dev/2003-May/035257.html __ http://mail.python.org/pipermail/python-dev/2003-May/035409.html `broke email date parsing`__ ... but it got fixed. .. __: http://mail.python.org/pipermail/python-dev/2003-May/035259.html `New thread death in test_bsddb3`__ This is a continuation from the `last summary`_. You can create as many thread states as you like as long as you only use one at any given point. .. __: http://mail.python.org/pipermail/python-dev/2003-May/035230.html `removing csv directory from nondist/sandbox - how?`__ Joys of CVS. You can never removed a directory unless you have direct access the the physical directory on the CVS root server. The best you can do is to empty the directory (make sure to get files named ".*") and assume people will do an ``cvs update -dP``. You can also remove the empty directories locally by hand if you like. .. __: http://mail.python.org/pipermail/python-dev/2003-May/035270.html `posixmodule.c patch to support forkpty`__ A patch was sent to python-dev incorrectly that tries to get os.forkpty to work on more platforms. It is now up on SourceForge_ and it is `patch #732401 <http://www.python.org/sf/732401>`__. .. __: http://mail.python.org/pipermail/python-dev/2003-May/035281.html .. _SourceForge: http://www.sf.net/projects/python `Timbot?`__ There is a real Timbot robot out there: http://www.cse.ogi.edu/~mpj/timbot/#Programming . .. __: http://mail.python.org/pipermail/python-dev/2003-May/035287.html `optparse docs need proofreading`__ What the 'subject' says. .. __: http://mail.python.org/pipermail/python-dev/2003-May/035288.html `heaps`__ This is a continuation of a thread from the `last summary`_. Lots of talk about heaps, priority queues, and other theoretical algorithm talk. It was felt that a more thorough API to allow for more fancy heap implementations would be helpful than what heapq provides. .. __: http://mail.python.org/pipermail/python-dev/2003-May/035343.html Weekly Python Bug/Patch Summary First one ended on `2003-05-04 <http://mail.python.org/pipermail/python-dev/2003-May/035292.html>`__. The second one ended on `2003-05-11 <http://mail.python.org/pipermail/python-dev/2003-May/035537.html>`__. `Distutils using apply`__ Since Distutils must be kept backwards-compatible (as stated in `PEP 291`_), it still uses 'apply'. This raises a PendingDeprecation warning which is normally silent unless you want all warnings raised. .. __: http://mail.python.org/pipermail/python-dev/2003-May/035293.html .. _PEP 291: http://www.python.org/peps/pep-0291.html `How to test this?`__ Dummy files can be checked into Lib/test . .. __: http://mail.python.org/pipermail/python-dev/2003-May/035318.html `Windows installer request...`__ Someone wanted the default drive on the Windows installer to be your boot drive and not C. It has been fixed. .. __: http://mail.python.org/pipermail/python-dev/2003-May/035319.html `Election of Todd Miller as head of numpy team`__ What the 'subject' says. .. __: http://mail.python.org/pipermail/python-dev/2003-May/035326.html `Startup time`__ Guido noticed that although Python 2.3 is already faster than 2.2, its startup time is slower. It looks like it is from failing stat calls. Speeding this all up is still being worked on. Prime suspects are the importation of codecs and re. .. __: http://mail.python.org/pipermail/python-dev/2003-May/035359.html `testing with and without pyc files present`__ Why does ``make test`` delete all .pyc and .pyo files before running the regression tests? To act as a large scale test of the marshaling code. .. __: http://mail.python.org/pipermail/python-dev/2003-May/035362.html `pyconfig.h not regenerated by "config.status --recheck"`__ ``./config.status --recheck`` doesn't work too well. .. __: http://mail.python.org/pipermail/python-dev/2003-May/035366.html `Python Technical Lead, New York, NY - 80-85k`__ Wrong place for a job announcement. .. __: http://mail.python.org/pipermail/python-dev/2003-May/035369.html `RedHat 9 _random failure under -pg`__ gcc ain't perfect. .. __: http://mail.python.org/pipermail/python-dev/2003-May/035386.html `SF CVS offline`__ ... but it came back up. .. __: http://mail.python.org/pipermail/python-dev/2003-May/035398.html `Microsoft speedup`__ It was noticed that turning on more aggressive inlining for VC6 sped up pystone by 2.5% while upping the executable size by 13%. Tim Peters noted that "A couple employers ago, we disabled all magical inlining options, because sometimes they made critical loops faster, and sometimes slower, and you couldn't guess which as the code changed". .. __: http://mail.python.org/pipermail/python-dev/2003-May/035454.html `Relying on ReST in the core?`__ Although docutils_ is not in the core yet, it is being used more and more. But is this safe? As long as it's kept conservative and not required anywhere, yes. .. __: http://mail.python.org/pipermail/python-dev/2003-May/035465.html `Make _strptime only time.strptime implementation?`__ As long as no one complains to loudly by 2.3b2, _strptime.strptime will become the exclusive implementation of time.strptime. _strptime.strptime also learned how to recognize UTC and GMT as timezones. .. __: http://mail.python.org/pipermail/python-dev/2003-May/035481.html `Building Python with .NET 2003 SDK`__ Logistix was nice enough to try to build Python on .NET 2003 and post notes on how he did it at http://www.cathoderaymission.net/~logistix/python/buildingPythonWithDotNet.… . .. __: http://mail.python.org/pipermail/python-dev/2003-May/035485.html `local import cost`__ Trying to find out how the cost of doing imports in the local namespace costs compared to doing it at the global level. .. __: http://mail.python.org/pipermail/python-dev/2003-May/035486.html `Subclassing int?`__ This thread started `two summaries ago <http://www.python.org/dev/summary/2003-04-01_2003-04-15.html>`__. Subclassing int to make it mutable just doesn't work. .. __: http://mail.python.org/pipermail/python-dev/2003-May/035500.html `patch 718286`__ Originally this summary was just going to be "The patch was applied". But no! Some of you actually want to know the patch is about. Geez! Isn't knowing that one more patch was closed enough for you people?!? I guess not! Well, the patch added support for the DESTDIR variable for auto-generated makefiles. .. __: http://mail.python.org/pipermail/python-dev/2003-May/035538.html `Need some patches checked`__ Some patches needed to be cleared by more senior members of python-dev since they were being handled by the young newbie of the group. Jeremy Hylton also mentioned that a full-scale refactoring of urllib2 is needed and would allow the closure of some patches. .. __: http://mail.python.org/pipermail/python-dev/2003-May/035540.html `os.path.walk() lacks 'depth first' option`__ Splinter threads: - `os.walk() silently ignores errors`__ This thread started in the `last summary`_. LookupError exists and subclasses both IndexError and KeyError. Rather handy when you don't care whether you are dealing with a list or dictionary but do care if what you are looking for doesn't exist. os.walk also gained a parameter argument called onerror that takes a function that will be passed any exception raised by os.walk as it does its thing; previously os.walk ignored all errors. .. __: http://mail.python.org/pipermail/python-dev/2003-May/035546.html __ http://mail.python.org/pipermail/python-dev/2003-May/035574.html `Random SF tracker ettiquete questions`__ Does python-dev care about dealing with RFEs? Sort of; it isn't a priority like patches and bugs, but cleaning them out once in a while doesn't hurt. Is it okay to assign a tracker item to yourself even if it is already assigned to another person? If the original person it was assigned to is not actively working on it, then yes. When should someone be put into the Misc/ACKS file? When they have done something that required some amount of brain power (yes, this includes one-line patches); some people, though, think it should take more. .. __: http://mail.python.org/pipermail/python-dev/2003-May/035549.html `codeop: small details (Q); commit priv request`__ Some issues with codec were worked out and Samuele Pedroni got commit privileges. .. __: http://mail.python.org/pipermail/python-dev/2003-May/035556.html `Python 2.3b1 _XOPEN_SOURCE value from configure.in`__ Python.h should always be included in extension modules first before any other header files. .. __: http://mail.python.org/pipermail/python-dev/2003-May/035560.html `Inplace multiply`__ Someone thought they had found a bug. Michael Hudson thought it was an old bug that was fixed. How did it end? Beats the heck out of me. =) .. __: http://mail.python.org/pipermail/python-dev/2003-May/035591.html `sf.net/708007: expectlib.py telnetlib.py split`__ A request for people to look at http://www.python.org/sf/708007 . .. __: http://mail.python.org/pipermail/python-dev/2003-May/035605.html `Simple dicts`__ Tim Peters suggested that if someone wanted something to do they could try re-implementing dicts to using chaining instead of open addressing. It turns out Damien Morton (who did a ton of work trying to optimize Python's bytecode) is working on an immplementation. .. __: http://mail.python.org/pipermail/python-dev/2003-May/035625.html `python/dist/src/Lib warnings.py,1.19,1.20`__ As part of the attempts to speed up startup time, the attempted elimination of the required import of the re module came up. This thread brought up the question as to whether it was desired to be able to pass a regexp as an argument for the -W command-line option for Python. .. __: http://mail.python.org/pipermail/python-dev/2003-May/035616.html `[PEP] += on return of function call result`__ You can't assign on the return value of a method calls. .. __: http://mail.python.org/pipermail/python-dev/2003-May/035640.html `Vacation; Python 2.2.3 release.`__ Guido is going on vacation and won't be back until May 26. He would like Python 2.2.3 to be out shortly after he gets back, although if it comes out while he is gone he definitely won't complain. =) You can get an anonymous CVS checkout of the 2.2 maintenance branch by executing ``cvs -d :pserver:anonymous@cvs.python.sourceforge.net:/cvsroot/python checkout -d <dir to store in> -r release22-maint python`` and changing the <> note to be the directory you want to put your CVS copy into. .. __: http://mail.python.org/pipermail/python-dev/2003-May/035642.html `MS VC 7 offer`__ At `Python UK`_ Guido was offered free copies of `Visual C++ 2003`_ by the project lead of VC, Nick Hodapp, for key developers (a free copy of the compiler is available at http://www.msdn.microsoft.com/netframework/downloads/howtoget.aspx ). This instantly led to the discussion of whether Python's binary distribution for Windows should be moved off of VC 6 to 7. The biggest issue is that apparently passing FILE * values across library boundaries breaks code. The final decision seemed to be that Tim, Guido, and developers of major extensions should get free copies. Then an end date of when Python will be moved off of VC 6 and over to 7 will be decided. None of this will affect Python 2.3 . This thread was 102 emails long. I don't use Windows. This was painful. .. __: http://mail.python.org/pipermail/python-dev/2003-May/035375.html .. _Python UK: http://www.python-uk.org/ .. _Visual C++ 2003: http://msdn.microsoft.com/visualc/

1 0

RELEASED Python 2.2.3c1
by Barry Warsaw May 22, 2003

May 22, 2003

I'm happy to announce the release of Python 2.2.3c1 (release candidate 1). This is a bug fix release for the stable Python 2.2 code line. Barring any critical issues, we expect to release Python 2.2.3 final by this time next week. We encourage those with an interest in a solid 2.2.3 release to download this candidate and test it on their code. The new release is available here: http://www.python.org/2.2.3/ Python 2.2.3 has a large number of bug fixes and memory leak patches. For full details, see the release notes at http://www.python.org/2.2.3/NEWS.txt There are a small number of minor incompatibilities with Python 2.2.2; for details see: http://www.python.org/2.2.3/bugs.html Perhaps the most important is that the Bastion.py and rexec.py modules have been disabled, since we do not deem them to be safe. As usual, a Windows installer and a Unix/Linux source tarball are made available, as well as tarballs of the documentation in various forms. At the moment, no Mac version or Linux RPMs are available, although I expect them to appear soon after 2.2.3 final is released. On behalf of Guido, I'd like to thank everyone who contributed to this release, and who continue to ensure Python's success. Enjoy, -Barry

1 0

Middleware2003: 16-20 June: Call for Participation
by Fabio M. Costa May 22, 2003

May 22, 2003

Please see the attached Call for Participation. Our apologies if you receive multiple copies. CALL FOR PARTICIPATION ACM/IFIP/USENIX INTERNATIONAL MIDDLEWARE CONFERENCE Rio de Janeiro, Brazil, 16-20 June 2003 http://middleware2003.inf.puc-rio.br Come to Rio to participate in the premier event on Middleware research and technology in 2003. Researchers, industrialists, and experts from all over the world will get together to present and discuss the recent advancements in Distributed Object Systems, Internet Technologies, and Middleware Platforms. Following the success of past conferences in this series (Lake District/UK, 1998, Palisades/NY, 2000, and Heidelberg/Germany, 2001), Middleware'2003 will host a very strong technical papers track featuring state of the art research in the field, as well as high-quality advanced workshops and a number of tutorials by technology experts. The conference will also include work-in-progress and posters sessions as well as social events. The location, Rio de Janeiro, is known as one of South AmericaŽs most outstanding areas of natural and historical beauty. REGISTRATION ============ Register online until May 15th and receive an early registration discount. For registration information visit http://middleware2003.inf.puc-rio.br/registration.htm TECHNICAL SESSIONS ================== A very strong technical papers track will feature state of the art research in the field (http://middleware2003.inf.puc-rio.br/programstruct.htm). Work-in-progress and Posters sessions will show promising ongoing work and experience reports. TUTORIALS ========= High quality tutorials by industry and university experts http://middleware2003.inf.puc-rio.br/tutorials.htm 1) J2EE vs. .NET Michael Stal Siemens AG, Corporate Technology, Munich, Germany 2) Peer-to-Peer Technologies Vana Kalogeraki University of California, Riverside, California, USA 3) Realization of Distributed Applications using MDA and the CORBA Component Model Marc Born and Tom Ritter Fraunhofer FOKUS, Berlin, Germany Phillipe Merle Unversity of Lille, Villeneuve d'Ascq, France 4) Object-Oriented Middleware and Components for the Grid Denis Caromel University of Nice Sophia Antipolois, France Christian Perez INRIA, France 5) Advanced Publish/Subscribe Services Alexander L. Wolf and Antonio Carzaniga University of Colorado, Boulder, Colorado, USA 6) Network and Web Services Security Concepts Using Java Raghavan N. Srinivas Sun Microsystems Inc., USA WORKSHOPS ========= 1) Middleware for Pervasive and Ad-Hoc Computing http://www.smartlab.cis.strath.ac.uk/MPAC/ 2) Reflective and Adaptive Middleware Systems http://tao.doc.wustl.edu/~corsaro/RM2003/ 3) Middleware for Grid Computing http://virtual01.lncc.br/mgc2003 4) Model-driven Approaches to Middleware Applications Development (MAMAD) http://www.dstc.edu.au/mamad-2003/ ORGANIZATION ============ General Chair: Carlos J.P. Lucena (PUC-Rio, Brazil) Program co-Chairs: Douglas Schmidt (Vanderbilt University, USA) Markus Endler (PUC-Rio, Brazil) Local Arrangements co-Chairs: Alexandre Sztajnberg (UERJ, Brazil) Renato Cerqueira (PUC-Rio, Brazil) WiP and Posters Chair: Guruduth S. Banavar (IBM T.J. Watson, USA) Advanced Workshops Chair: Gordon Blair (Lancaster University, UK) Tutorials Chair: Frank Buschmann (Siemens AG, Germany) Publicity co-Chairs: Fabio Costa (UFG, Brazil) Fabio Kon (IME-USP, Brazil) FOR MORE INFORMATION ==================== For further information, please visit the conference home page: http://middleware2003.inf.puc-rio.br If you have any question contact the local arrangements chairs, Alexandre Sztajnberg (alexszt(a)uerj.br) or Renato Cerqueira (rcerq(a)inf.puc-rio.br). Middleware'2003 is partially sponsored by Sony and IBM. We hope to see you in Rio in June!

1 0

Kodos 1.5 - Python regular expression debugger
by stuff＠nonpoint.mailzilla.net May 22, 2003

May 22, 2003

Kodos 1.5 has been released and is available at: http://kodos.sourceforge.net Changes since 1.3: - New feature: examine regex has been added. The examine feature is useful in the event when a regex that you have been editing no longer matches the text string. In some instances you may have inadvertantly added a character. Normally, the only indication that you have that the regex doesn't match is the status bar indicator. Although this alone may be useful, Kodos provides the examine feature to help pinpoint errors. By examining the regex, Kodos will locate the longest possible match by scanning the current regex. - Bug fixes: the clear all option behaves better - Help: the help section has been redone. About Kodos: Kodos is a regular expression designer, tester, debugger and validator that allows a developer to create and modify regular expressions against a test string. The intuitive grahpical interface allows the developer the ability to modify the regular expression (regex) and to see the effects against their test string in real-time. Key Features: - Matches can be easily viewed and each match can be seen distinctly - Regex groups and named groups are clearly displayed - Sample source code is shown so even python developers new to regular expressions can quickly add the produced regular expressions to their own projects. - Ability to load and save your test cases - Kodos relies on PyQt for the GUI elements. http://kodos.sourceforge.net

1 0