From pep308vote@hotmail.com  Sun Mar  2 10:27:15 2003
From: pep308vote@hotmail.com (Raymond Hettinger)
Date: 2 Mar 2003 02:27:15 -0800
Subject: Vote on PEP 308:  Ternary Operator
Message-ID: <mailman.1046609650.884.clpa-moderators@python.org>

BASICS
------
Vote by email no later than Noon (EST) on Sunday, March 9, 2003.
Use the following format:

  To:       pep308vote@hotmail.com
  Subject:  PEP308
  From:     <valid email address>
  Line 1:   <letter of most preferred format> <accept or reject> <format>
  Line 2:   <letter of second best format> <accept or reject>  <format>
  Line 3:   <letter of third best format>  <accept or reject>  <format>
  Line 4:   <full name of voter>
  Line 5:    <example 1>
  Line 6:    <example 2>
  Line 7:    <example 3>
  Line 8:    <example 4>
  Line 9:    <example 5>

Every line is required.
The published results will only include lines 1, 2, 3, and 4.
Note, that means your name is published.
You can use a fake name but a real name is preferred.

The email address is used for:
    assuring only one vote per address.
    notification of an improperly formatted ballot.
    resolving any questions that arise about the vote process.

Write-out these five examples using your most preferred syntax:
    x = "door" + (if quantity>1: "s" else: "")
    data = (if hasattr(s, 'open'): s.readlines() else: s.split())
    z = 1.0 + (if abs(z) < .0001:  0 else: z)
    t = v[index] = (if t<=0: t-1.0 else: -sigma /(t + 1.0))
    return (if len(s)<10: insertsort(s) else: quicksort(s))
Note, the examples are required but will not be used.
Try to get them right, but it is okay if they are wrong.

Marking accept means that you prefer this format over no-change.
Marking reject means that you prefer no-change, but if there is
one, then the marked choice would be the best one.

CHOICES (taken from Erik Max Francis's posting of seconded choices)
-------
A.  x if C else y
B.  if C then x else y
C.  (if C: x else: y)
D.  C ? x : y
E.  C ? x ! y
F.  cond(C, x, y)
G.  C ?? x || y
H.  C then x else y
I.  x when C else y
J.  C ? x else y
K.  C -> x else y
L.  C -> (x, y)
M.  [x if C else y]
N.  ifelse C: x else y
O.  <if C then x else y>
P.  C and x else y
Q.  any write-in vote

Note 1:  All of these options have short-circuit behavior.
That means that cond(C,x,y) would be a special syntax.

Note 2:  All options are eligible.  If the PEP notes that a proposal
had been rejected at some point, then consider it revived.


SAMPLE BALLOT
-------------
C accept  (if c: x else: y)
D reject  c ? a : b
H reject  c then a else b
John Jones
x = "door" + (if quantity>1: "s" else: "")
data = (if hasattr(s, 'open'): s.readlines() else: s.split())
z = 1.0 + (if abs(z) < .0001:  0 else: z)
t = v[index] = (if t<=0: t-1.0 else: -sigma /(t + 1.0))
return (if len(s)<10: linsort(s) else: qsort(s))


RATIONALE AND PROCESS
---------------------
In the end, only Guido's vote counts. The purpose of the voting is
to provide him with information about how the community feels.

The goal of collecting preferences along with accept/rejects is to
allow everyone (including those who prefer the status quo) to
also be able to express which syntax they find least objectionable.
The end result is that Guido will know which is the most preferred
syntax AND the how much it is preferred to the status quo.

The purpose of publishing both names and the votes is to provide
assurance that the process is honest.  Also, I think that people
are more careful in their voting if they publicly take a position.
However, if someone wants to vote in secret, they are welcome to
use a pseudonym; at least, they will see their chosen name on the
tally and know their vote was counted.

The purpose of the examples section is voter education.  This
provides some assurance that each voter has at least tried
their own preferred syntax.


EXCEPTION HANDLING
------------------
If there is a dispute, I'll ask Laura Creighton to resolve it.
Her decision will be final.

If I messed-up the ballot, I will repost a correction.

If the email account fails, I will open a new one and extend
the voting by a day.

If you make a mistake or change your mind, you may re-submit
your vote and the previous vote will be thrown out.

If there are any questions or discussion, please use the newsgroup.
The email address listed above is only for ballots.


Vote Early.  Vote Once.

Raymond Hettinger


From gerald@vamphq.com  Sun Mar  2 16:07:39 2003
From: gerald@vamphq.com (Gerald Bauer)
Date: 2 Mar 2003 08:07:39 -0800
Subject: Python and XUL: Luxor XUL Python Example Suite Released
Message-ID: <mailman.1046652722.3681.clpa-moderators@python.org>

The Luxor XUL (XML User Interface Language) Python example suite is
now available and includes a mini calculator, a channel surfer, a
counter and more.

  Grab a copy at http://sourceforge.net/project/showfiles.php?group_id=28946
(look for the luxor-python-examples package).

  Here's a sneak preview:

counter.xul:
================================
<xul>
  <vbox id="COUNTER">
    <groupbox>
      <caption label="Counter"/>
      <textbox id="DISPLAY"
         style="align: center; color: yellow; background: black; font:
24 bold monospace;" />
    </groupbox>
    <hbox>
      <button label="Dec (-)" command="dec" style="width: 90px" />
      <button label="Clear" command="clear" style="width: 90px" />
      <button label="Inc (+)" command="inc" style="width: 90px" />
    </hbox>
  </vbox>
</xul>

counter.py
================================
# -- cut --

class CounterForm( XulForm ):
  def __init__( self ):
    XulForm.__init__( self, "COUNTER" )
    self.setup()

  def init( self ):
    self.display = XulInput( self, "DISPLAY" )

  def setCounter( self, counter ):
    self.display.text = str( counter )

class AppFrame( JFrame ):

  def __init__( self ):
    JFrame.__init__( self, "Luxor Counter Example" )

    DynXulAction( "inc", self.onIncCounter )
    DynXulAction( "dec", self.onDecCounter )

    xul = XulMan( "c:/sandbox/python/src/counter/chrome" )

  def onIncCounter( self ):
    self.counter += 1
    self.updateCounter()

  def onDecCounter( self ):
    self.counter -= 1
    self.updateCounter()

# -- cut --

  That's it. Enjoy.

  - Gerald (Luxor Project Lead)

PS: What is XUL?

To get started with XUL (XML User Interface Language) check out the
Richmond Post XUL Link-opida online @
http://luxor-xul.sourceforge.net/post/links.html

PSS: What is Luxor?

Luxor is an open-source XML User Interface Language (XUL) toolkit in
Java that supports handpicked Mozilla XUL goodies and includes a web
server, a portal engine (supporting RSS), a template engine
(Velocity), a scripting interpreter (Python) and more. For more info
check out the Luxor site @ http://luxor-xul.sourceforge.net


From Rimon Barr <rb83@cornell.edu>  Mon Mar  3 01:18:43 2003
From: Rimon Barr <rb83@cornell.edu> (Rimon Barr)
Date: Sun, 2 Mar 2003 20:18:43 -0500 (EST)
Subject: spyce v1.3.9 released
Message-ID: <mailman.1046695921.7374.clpa-moderators@python.org>

Spyce v1.3.9 released on 1 March 2002

SPYCE is a server-side language that supports simple and efficient
Python-based dynamic HTML generation. Those who are familiar with JSP,
PHP, or ASP and like Python, should have a look at Spyce. Its modular
design makes it very flexible and extensible. It can also be used as a
command-line utility for static text pre-processing.

Get it at:
  http://spyce.sourceforge.net

Changes since the previous release annoucement (v1.3.5):
  - improved built-in webserver
  - added support for ASP/JSP-like syntax
  - minor fixes and documentation updates

Enjoy,
Rimon.


Change log:
v1.3.9
  spyceWWW web server improved
    - configuration options integrated into spyce.conf
    - handler mechanism created
    - defined spyce and dump handlers
    - reads Apache format mime-type definition files
    - .spy files ==> spyce handler; rest ==> dump handler
    - can display directory listings
    - configuration options added accordingly
    - corresponding documentation changed
  documentation restructured to explain common configuration file
    options in the runtime section
  fix: docs/examples/*.gif added to rpm and windows installer
  expanded section on how to get Spyce running under IIS via CGI

v1.3.8
  user request:
    modified request.get/post/get1/post1/env() to accept default values
    (note: will break code that provided caseInsensitive parameter by
      position)
    added request.getpost/getpost1/postget/postget1/default() methods
  bug fixes: python 1.5 backwards compatibility issues in the following
    online examples: gif.spy, myPortal.spy, mysession.spy

v1.3.7
  support for ASP-style delimeters -- <% %>
  use of Bastion eliminated, due to Python deprecation

v1.3.6
  info.spy example updated to deal with implicitly loaded taglib module
  minor documentation fix for doc-mod_include
  quotes for the PythonPath in httpd.conf





From lkcl@samba-tng.org  Mon Mar  3 10:09:47 2003
From: lkcl@samba-tng.org (Luke Kenneth Casson Leighton)
Date: Mon, 3 Mar 2003 10:09:47 +0000
Subject: [ANN] custom 0.7.1 released
Message-ID: <mailman.1046695922.7378.clpa-moderators@python.org>

Custom 0.7.1
------

	custom is an e-commerce solution for small to medium-sized
	businesses that provides:
	
	- a customisable web front-end for customers and
	  Point-of-Sale staff to place orders
	  
	- for warehouse staff to manage stock
	
	- for accountants and sales staff to manage and generate invoices
	
	- for purchasing managers to keep track of suppliers and
	  competitive pricing.

Download
--------

	http://sf.net/projects/custom


OS Requirements
---------------

	Custom is a pure Python application.  Therefore it is entirely
	your choice as to what OS you use, but it must obviously run
	python (see http://python.org).  Python is known to run on
	Linux, all version of Unix, all the BSDs, BEOS, MAC/OS 10,
	and many others.

Additional Features
-------------------

	The major changes since 0.6 are the inclusion of product
	reconciliation scripts.  Stock from multiple suppliers
	results in products with the same name: the database
	becomes quickly unmanageable...

	The major changes since 0.5 are the use of HTML templates
	which may be modified at the webmaster's discretion,
	independent of the source code.


Security Considerations (Internet use only)
-----------------------

	Please note that if you intend to put Custom on an Internet
	Server that you should consult with a security expert regarding
	your implementation, paying particular attention if you are in
	the UK to the Data Protection Act.

	Your choice of OS and your implementation of Custom should
	reflect your willingness to ensure that your customers'
	confidentiality (and credit card details) is protected from
	hackers.

	In other words, being blunt and spelling it out: please don't
	install Custom on a default installation of Windows with no
	security patches, no firewall, and then expect it to stay up
	on the Internet without getting hacked.

	Your data is ENTIRELY your responsibility.  By Law.


Software Requirements
---------------------

	This package requires or uses some additional software
	packages, which can all be obtained as RPMs, Debian
	Packages or compiled from Source if you feel the need.
	At each site, RPMs, DEBs and source are all typically
	available for download.

	RPMs can be found using rpmfind.net; Debian packages
	can be found using apt-cache search <packagename>,
	using dselect or going to debian.org; and the Source
	packages are available individually at the URLs shown
	below.

	You should always ensure that, if you are putting Custom
	on an Internet Server, that the latest security fixes have
	been applied (on an on-going basis), and that you keep
	up-to-date with security alerts, e.g. from bugtraq and
	NTbugtraq.


	Of particular note is that if you wish to use a separate
	SQL database server, then obviously you need to install
	the client-side SQL access software on the Custom server,
	but you will clearly not need to install the SQL server
	software on the same machine.

	You will need:

	- An up-to-date web server capable of SSL (if you need it)
	  and also capable of running CGI-bin scripts.  e.g. Apache2
	  (http://apache.org)

	- Python 2.1 or greater
	  (http://python.org)

	- the pysqldb package version 0.5 or greater
	  (http://sf.net/projects/pysqldb)

	- EITHER:

		- MySQL client libraries
		(http://mysql.org)

		- Andy Dustman's MySQLdb package (requires MySQL client)
		  (http://sf.net/projects/mysqldb)

	  OR:

		- Pysxqmll (a Python / MS-SQL / XML client for MS-SQL 2000)
		(http://sf.net/projects/pysxqmll) [what a stupid name.]

	- The mxDateTime and DateTime packages 
	  (http://starship.skyport.net/~lemburg/mxDateTime.html)

	- PyCrypto version 1.9a1 or greater
	  (http://sf.net/pycrypto) 

	- Python HTML-TMPL (generates HTML from templates)

	In case you were wondering, PostgreSQL and SAPdb are under
	investigation to be added into the database abstraction
	system that custom uses.

	custom uses some features in the SocketServer class that
	were introduced in Python 2.1.

	If you wish to stick with Python 2.0, you may wish to
	copy over the SocketServer.py file from the distribution
	of Python 2.1 or greater, and use that (making sure that
	you back up your original SocketServer.py file!)

Debian install
------

	It's a lot easier if you are using Debian: here is a list of
	the package names.  It'll be even easier once the Debian
	packaging is released.

	- python-crypto
	- python-egenix-mxdatetime
	- python-mysqldb
	- python-htmltmpl
	- apache or apache2

	If you install the three python packages using apt-get or dselect,
	that should be enough to pull in all the dependencies
	(including Python 2.2 and MySQL)

	The development of the debian "custom" package is presently
	underway.


SQL
---

	You must also install MySQL or MS-SQL 2000 on a server,
	where you may wish to install the SQL server on a
	separate system.

	If you do so, as noted above you will need to put the
	MySQL or MS-SQL client libraries onto the Custom Server
	and

	For various reasons, a high-availability cluster pair is
	recommended for your SQL system, under which circumstances,
	if you are considering HA, you CAN install the custom
	package on the same box as the SQL database - if you know
	what you are doing (otherwise, run only one Custom server
	and use a separate SQL cluster).

	You WILL be able to run the Back Office program monitord.py,
	on a HA cluster, because it is designed to cope with several
	concurrent copies of monitord.py running off the same SQL
	server.


Optional requirements
---------------------

	A barcode scanning device, such as those available from
	Worth Data (www.pcbarcode.com) that reads EAN and other
	barcodes and pretends to be a USB keyboard, proves to
	be very useful.

	If you are running Linux, install the full HID USB
	device module and the Input Device and Keyboard
	support modules:

		CONFIG_INPUT=m
		CONFIG_INPUT_KEYBDEV=m
		CONFIG_USB_HID=m

	Do not be fooled into installing the partial HID USB
	keyboard device (CONFIG_USB_KBD) on its own, because
	it won't work, you MUST install the full HID support.



From alan_salmoni@yahoo.com  Mon Mar  3 10:38:46 2003
From: alan_salmoni@yahoo.com (Alan James Salmoni)
Date: 3 Mar 2003 02:38:46 -0800
Subject: ANN: New release of SalStat Statistics Package
References: <mailman.1046383504.17812.clpa-moderators@python.org>
Message-ID: <mailman.1046695922.7379.clpa-moderators@python.org>

Oops! My mistake - I forgot to upload the file as a binary and the
downloads were therefore corrupted. This has now been rectified, and
the downloads are available and should work.

Apologies to anyone whose time I have wasted.

Alan.

alan_salmoni@yahoo.com (Alan James Salmoni) wrote in message news:<mailman.1046383504.17812.clpa-moderators@python.org>...
> Hi all,
> 
> Following a release the other day, there is a new release of the
> SalStat Statistics Package written in Python with wxPython, Numeric
> and SciPY.
> 
> From the website (http://salstat.sunsite.dk), there is a source
> download (http://salstat.sunsite.dk/salstat.20030227.zip - 439k) which
> needs Python, wxPython, Numeric, SciPy (and I believe PIL) to be
> installed. For Windows users, there is a self-installing executable
> made with the McMillan installer and the Inno installer (thanks to the
> guys who wrote these!) available from
> http://salstat.sunsite.dk/salstat.20030227.setup.exe (7.78MB).
> 
> This version allows chi square tests (observed in the first column,
> expected in the second column of the 2 condition test dialog), better
> graphs (thanks to SciPy plt function), and the interface has been
> spruced up a bit more. It loads ASCII files generally well, but don't
> leave too many blank spaces where there should be missing data.
> 
> Thanks to all who have helped in one way or another. The next version
> should features multi-factorial anova with simple and main effects
> easily accessible from the interface (no syntax files needed!).
> 
> Feedback is requested regarding test accuracy and interface
> experience. Please fire (not flame!) away as I have had little
> feedback about the interface lately (either I'm doing something very
> right, or very wrong indeed!)
> 
> Have fun!
> 
> Alan James Salmoni
> SalStat Statistics
> http://salstat.sunsite.dk


From srackham@methods.co.nz  Mon Mar  3 22:24:41 2003
From: srackham@methods.co.nz (Stuart Rackham)
Date: 3 Mar 2003 14:24:41 -0800
Subject: ANN: AsciiDoc 2.0 released
Message-ID: <mailman.1046741342.15941.clpa-moderators@python.org>

AsciiDoc
--------
AsciiDoc is a text document format for writing articles, manuals and
UNIX man pages. AsciiDoc files can be translated to HTML (with or
without stylesheets), DocBook (articles, books and refentry documents)
and LinuxDoc using the asciidoc(1) command. AsciiDoc can also used to
build and maintain websites.

asciidoc(1) can be extended and customised to output any SGML/XML markup,
this is because all asciidoc(1) translation rules are contained in
cascading text based configuration files.

Requisites
----------
Python 1.5.2 or higher.

Obtaining AsciiDoc
------------------
The latest AsciiDoc version and online documentation can be found at
the AsciiDoc website http://www.methods.co.nz/asciidoc/

AsciiDoc is also hosted at the SourceForge at
http://sourceforge.net/projects/asciidoc/


Best regards,
---
Stuart Rackham <srackham@methods.co.nz>


From stuff@mailzilla.net  Tue Mar  4 01:31:58 2003
From: stuff@mailzilla.net (Phil)
Date: 3 Mar 2003 17:31:58 -0800
Subject: Kodos 0.9 released (python regular expression GUI)
Message-ID: <mailman.1046785322.3114.clpa-moderators@python.org>

Kodos 0.9 has been released and is available at:

http://kodos.sourceforge.net

Kodos is a regular expression tester, debugger and validator that
allows a developer to create and modify regular expressions against a
test string.  The intuitive interface allows the developer the ability
to modify the regex and to see the effects 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.

To read more detailed information, view screenshots and download Kodos
please
visit:  http://kodos.sourceforge.net


From npetry@accesscomm.ca  Tue Mar  4 23:55:48 2003
From: npetry@accesscomm.ca (Norman Petry)
Date: 04 Mar 2003 17:55:48 -0600
Subject: ANN: Ballot for Complementary PEP308 Ternary VOTE
Message-ID: <mailman.1046824203.18216.clpa-moderators@python.org>

IMPORTANT NOTE:

This is NOT a ballot for the "official" PEP-308 vote being run by
Raymond Hettinger.  It is for a different vote that is intended to
COMPLEMENT the results of the official vote, by using a different type
of ballot, and a different method of tallying the results (Condorcet's
Method), for those who may be interested.  If enough people choose to
participate, it will provide a high-quality source of additional
information about the preferences of the Python community regarding the
ternary operator.

This vote is NOT intended to compete with, or substitute for the
official vote.  Please participate in both votes if you have the time,
but BE SURE to vote in the official one if you care about the outcome of
PEP-308.  See the explanations in my posting to comp.lang.python two
days ago for more information about the reasons for this supplemental
vote on PEP-308 ("ANNOUNCE: Complementary VOTE re: PEP 308 Ternary
Proposal", Sun, 02 Mar 2003 17:44:33 -0600).
 

NOMINATIONS

The two-day nomination period for additional syntax proposals has now
ENDED.  No additional nominations were received, so the ballot is as
follows:


BALLOT

----------
XX  NO TERNARY
XX  t if C else f
XX  if C then t else f
XX  (if C: t else: f)
XX  if C: t else: f
XX  C ? t : f
XX  C ? t ! f
XX  cond(C, t, f)  
XX  C ?? t || f
XX  C then t else f
XX  t when C else f
XX  C ? t else f
XX  C -> t else f
XX  C -> (t, f)
XX  [t if C else f]
XX  ifelse C: t else f 
XX  select C: t else f 
XX  when C: t else f   
XX  case C: t else f   
XX  <if C then t else f>
XX  C and t else f
----------


HOW TO VOTE

Voting is a simple matter of RANKING the alternatives of interest by
replacing the 'XX' that precedes each option with a 2-digit number.  For
example, you would use '01' for your FAVOURITE (highest-ranked) option,
and greater numbers (02, 03,...) for lower-ranked alternatives.

You may RE-ORDER the options on the ballot.  It is often easier when
there are many options to reorder them manually from best to worst, and
then assign rankings.  Note though, that you must STILL assign a rank
number to each option, since it is always the NUMBER that determines the
rank, not the ordering.

You may assign the SAME RANK to multiple options if you consider them to
be equally good/bad.  Doing this is equivalent to abstaining from
participation in any decision between these equally-ranked alternatives.

To simplify voting, you may TRUNCATE your ballot by leaving certain
options UNRANKED (for any options you consider to be so bad and
unwinnable as to not be worth considering).  If you wish to do this,
either:
a) leave 'XX' in front of the unwanted option(s) in your submitted
ballot, rather than replacing it with a rank number, or
b) delete the line(s) of the ballot that contain the unwanted options.
You can also use a combination of both methods.  In either case, these
truncated options will be interpreted the same as if they had been
ranked EQUALLY, and LOWER than all explicitly ranked alternatives.  

While truncation and equal rankings provide convenience, ranking many
options (even those you dislike) is a good idea.  See the STRATEGY TIPS
section (below) for reasons why.

Note that the status quo option of "NO TERNARY" simply appears as one of
the available options, and every other proposed syntax appears as a
separate option on the ballot.  By placing "NO TERNARY" somewhere within
the middle of your ranking, you can express the desire to have a ternary
operator added to Python only if certain forms of syntax are used, and
reject alternatives that you dislike (while still expressing preferences
among these bad alternatives, in case one or more of them proves to be
winnable).  The status quo option can of course also be ranked first or
last, if you feel either that (a) no ternary is acceptable in any form,
or alternately, (b) should be added to the language at any cost.  

A sample completed ballot might look like:

----------
02  (if C: t else: f)
01  t if C else f
02  NO TERNARY
XX  if C then t else f
03  if C: t else: f
----------

Here, the voter's favourite option is "t if C else f".  The 4th option
is unranked, and could have instead been deleted to indicate the same
thing.  Surrounding lines of hyphens marking the beginning and end of
the ballot are appreciated for clarity, but not required.


SUBMITTING YOUR BALLOT

You may vote by submitting your email ballot to:

------------------
pepvote@canada.com
------------------

Your final vote must be received within 96 HOURS (4 days, approx.
Wed-Sat) of the time this message appears on comp.lang.python and/or
comp.lang.python.announce for it to be counted in the final result.

A CONFIRMATION message will be returned for each ballot that is
received, identifying any problems.  Unconfirmed ballots will not appear
in the results, so if you don't receive a reply within a few hours, you
may wish to send your ballot again (I'm confirming votes manually, so
the response will not be immediate).  

If you decide to CHANGE YOUR VOTE, just send a revised ballot containing
your new preferences.  The last confirmed ballot for each email address
will be the one that appears in the final results.


RESULTS

Results will be published on Sunday, March 9th, but NOT before the
voting period of the "official" vote has ended (Noon, EST).  Published
results will be sent to comp.lang.python and comp.lang.python.announce.

Results will include (among other things) a list containing each voter's
NAME, EMAIL ADDRESS (munged), and COMPLETED BALLOT to allow for
independent verification.  Therefore, if you do not want any or all of
this information about you made public, DO NOT VOTE!  Please refer to
the previous message announcing this vote for details about what types
of information will appear in the results.


STRATEGY TIPS

You may be unfamiliar with CONDORCET'S METHOD, the system of voting used
here (unless you happen to be a member of the Debian Project :-). 
Although completing a ranked ballot is technically very easy, if you
wish to know how to maximise the chances of getting the outcome you
want, you should read following information before completing your
ballot:

*****

1. Condorcet's method of counting ranked ballots is very different from
other systems (STV/AV/IRV, Borda, etc.) that also use a ranked ballot. 
Therefore, it is a bad idea to attempt to vote strategically based on
what you know (or think you know) about how those systems work.  The
best strategies for one method of voting will usually fail very badly
when applied in another, even if the form of the ballot is similar.

2. You should NOT assume that ranking any UNACCEPTABLE options will harm
the chances of electing your PREFERRED option(s).  Condorcet's method is
a system of pairwise voting, where the overall result is determined by
finding the majority winners of a series of two-way races between every
possible pair of alternatives.  Not ranking (truncating) some options,
or assigning the same rank to a group of options is therefore equivalent
to ABSTAINING from participation in any decision between those
equally-ranked alternatives.  Therefore, if the final choice in the
election is between two options, both of which you dislike -- but not
EQUALLY -- you may later regret not having participated in that
decision.

3. You should also NOT vote for what you believe to be an acceptable,
popular choice (the "lesser evil" compromise) ahead of your true
favourite(s), in the belief that this will somehow help to prevent the
election of a popular, disliked alternative (the "greater evil").  This
type of strategy is often necessary in plurality ("first-past-the-post")
voting, but is ineffective and unnecessary with Condorcet's method. 
Condorcet's method finds the best compromise automatically, if one is
needed, so doing this will simply harm the chances of electing your true
favourite.  See http://www.electionmethods.org/Condorcet.htm for a
detailed explanation of this.

*******************************************************
With CONDORCET'S METHOD, you will maximise the power and effectiveness
of your ballot by providing a COMPLETE and SINCERE expression of your
true preferences.  You should only rank options equally if you genuinely
consider them to be equally good (or bad).
*******************************************************

--
Norman Petry




From pep308vote@hotmail.com  Wed Mar  5 01:36:44 2003
From: pep308vote@hotmail.com (Raymond Hettinger)
Date: 4 Mar 2003 17:36:44 -0800
Subject: Vote on PEP 308:  Addenda
Message-ID: <mailman.1046829076.18615.clpa-moderators@python.org>

Several people have requested a short-way
to express that they do not want any ternary operator.
Here it is:

Send a email to pep308vote@hotmail.com
with a subject of PEP308:
    Line 1:  I reject all alternatives.
    Line 2:  <Your full name>


That is simple and is easily tabulated.
You may, of course, stick with the original procedure.

There were also those whose wished to express some
sort of opinion that was not expressable on the ballot.
They are welcome to submit a custom vote and I'll
accumulate those separately.  For example:
    Line 1:  I don't care about the outcome
    Line 2:  <Your full name>


Raymond Hettinger


From anthony@computronix.com  Wed Mar  5 19:06:17 2003
From: anthony@computronix.com (Anthony Tuininga)
Date: 05 Mar 2003 12:06:17 -0700
Subject: cx_Oracle download issues
Message-ID: <mailman.1046901602.22231.clpa-moderators@python.org>

Due to a security "enhancement" by Microsoft for IIS, files to be
downloaded may not end in .exe. The installer files are being renamed to
.exe.bbb which bypasses the "security check" so remove the phony
extension upon download. My apologies for the inconvenience but my
company uses IIS for its web site.

On that note, a while ago someone mentioned that they would be willing
to host the binaries for me. If that is still a possibility please
contact me and I'll see what can be arranged. Thanks.

-- 
Anthony Tuininga
anthony@computronix.com
 
Computronix
Distinctive Software. Real People.
Suite 200, 10216 - 124 Street NW
Edmonton, AB, Canada  T5N 4A3
Phone:	(780) 454-3700
Fax:	(780) 454-3838
http://www.computronix.com



From Thomas Guettler <thomas@thomas-guettler.de>  Wed Mar  5 21:51:25 2003
From: Thomas Guettler <thomas@thomas-guettler.de> (Thomas Guettler)
Date: Wed, 5 Mar 2003 22:51:25 +0100
Subject: OOPServer 0.1 Released
Message-ID: <mailman.1046901603.22240.clpa-moderators@python.org>

This is the 0.1 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. It can be viewed as an
example of how you can program Python products with Zope. The
implementation of OOPServer is 100% Python and avoids DTML, ZPT and
Acquisition.

You can get the source from:
 http://guettli.sourceforge.net

A demo is available:
 http://guettli.dyndns.org:8080

Changes since the last release:

 - Keyword-List in the demo can be edited
 - Nicer tables (CSS)
 - DemoObject has more metadata
 - Changes to OOPObjects are logged  
   (You know how has changed the object at what time)
 - i18n: Internationalisation: Available in German and English
 - Code clean up

 Thomas Guettler


-- 
Thomas Guettler <guettli@thomas-guettler.de>
http://www.thomas-guettler.de



From wesc@fuzzyorange.com  Thu Mar  6 02:27:12 2003
From: wesc@fuzzyorange.com (Wesley Chun)
Date: Wed, 5 Mar 2003 18:27:12 -0800 (PST)
Subject: ANN: Python II course (Silicon Valley, CA)
Message-ID: <mailman.1046954702.32417.clpa-moderators@python.org>

this coming quarter, i'll be teaching Python II instead of
Python I for a little variety.  it will be a very informal
class based around a variety of advanced topics in Python.

if u or anyone u know would be interested in it, please check
out the course description or signup at the URL down below.

"Python Programming II:  Advanced Topics in Python"
UC Santa Cruz, Spring Quarter 2003
Apr 14 - Jun 16, 2003 (except May 26 and TBD)
Monday nights, 6:30 - 9:30pm
Sunnyvale, California in Silicon Valley

http://artemis.ucsc-extension.edu/~wesc/024d50cd.htm

Register online, or contact Sherry at 408-861-3765 or
smirkarimi@ucsc-extension.edu to enroll.

hope 2 c some of u there!

-wesley

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

"Core Python Programming", Prentice Hall PTR, =A9 2001
    http://starship.python.net/crew/wesc/cpp/

Silicon Valley-San Francisco Bay Area Python Users Group (BayPIGgies)
    http://www.baypiggies.net

wesley.j.chun :: wesc at deirdre.org or wesc at fuzzyorange.com
cyberweb.consulting : henderson, nv : cyberweb at rocketmail.com
http://roadkill.com/~wesc/cyberweb/



From logistix@zworg.com  Thu Mar  6 03:13:22 2003
From: logistix@zworg.com (logistix)
Date: 5 Mar 2003 19:13:22 -0800
Subject: PyXR 0.8- Cross-Referenced HTML from Python Source
Message-ID: <mailman.1046954703.32424.clpa-moderators@python.org>

PyXR generates HTML pages from python source files.  It also attempts
to generate cross-referenced hyperlinks, which hopefully makes it
distinctive from the 8 million other prettyprinters out there.  It's
been tested on Python 2.2 and 2.3 for Windows, OpenBSD 3.2 and RedHat
7.3.  There's no reason it shouldn't work on other platforms with
minor configuration.

More information is available at:

    http://members.bellatlantic.net/~olsongt/python/pyxr.html

The package is available at:

    http://members.bellatlantic.net/~olsongt/python/PyXR.zip

I've also posted some sample output (but expect some 404's because of
space considerations):

    http://members.bellatlantic.net/~olsongt/python/PyXRsample/

Enjoy!


From pep308vote@hotmail.com  Thu Mar  6 19:35:09 2003
From: pep308vote@hotmail.com (Raymond Hettinger)
Date: 6 Mar 2003 11:35:09 -0800
Subject: Update on the ternary operator vote
Message-ID: <mailman.1046980888.2030.clpa-moderators@python.org>

About 360 votes have been received to date
and the submission rate is not yet falling off.

If I had it to do over, the ballot would be simpler,
but it seems to be working out okay none-the-less.
So far, almost every vote has been absolutely clear in its intent.
I've had to mail fewer than ten requests for clarification
(mostly for empty emails or for omitted names).
A few people hated filling out the examples
but some thought it was a great idea -- c'est la vie.

The one surprising comment is that some newsgroup
readers had filtered out all posts with the word "ternary"
or "308" and, as a result, did not see the vote announcement.

There have been a handful of requests to post
intermediate results.  Others have assured me
that is a bad idea.  Accordingly, results
won't be posted until all the votes are in.

I can reveal that the results are not lopsided
and it is still worth a few minutes to vote.


Raymond Hettinger



"A man with two watches never knows what time it is."


From jason@tishler.net  Thu Mar  6 22:18:07 2003
From: jason@tishler.net (Jason Tishler)
Date: Thu, 06 Mar 2003 17:18:07 -0500
Subject: Updated Cygwin Package: python-2.2.2-6
Message-ID: <mailman.1046993462.32632.clpa-moderators@python.org>

New News:
=== ====
I have updated the version of Python to 2.2.2-6.  The tarballs should be
available on a Cygwin mirror near you shortly.

The only purpose of this release is to rebuild against the latest Cygwin
OpenSSL package, 0.9.7a-1.  Otherwise, this package should be identical
to the previous one.

Old News:
=== ====
Python is an interpreted, interactive, object-oriented programming
language.  If interested, see the Python web site for more details:
                                                                   
    http://www.python.org/                                         

Please read the README file:
                            
    /usr/doc/Cygwin/python-2.2.2.README

since it covers requirements, installation, known issues, etc.

To update your installation, click on the "Install Cygwin now" link on
the http://cygwin.com/ web page.  This downloads setup.exe to your
system.  Then, run setup and answer all of the questions.

Note that we have recently stopped downloads from sources.redhat.com
(aka cygwin.com) due to bandwidth limitations.  This means that you will
need to find a mirror which has this update.

In the US,
ftp://mirrors.rcn.net/mirrors/sources.redhat.com/cygwin/
is a reliable high bandwidth connection.

In Germany,
ftp://ftp.uni-erlangen.de/pub/pc/gnuwin32/cygwin/mirrors/cygnus/
is usually pretty good.

In the UK,
http://programming.ccp14.ac.uk/ftp-mirror/programming/cygwin/pub/cygwin/
is usually up-to-date within 48 hours.

If one of the above doesn't have the latest version of this package
then you can either wait for the site to be updated or find another
mirror.

The setup.exe program will figure out what needs to be updated on your
system and will install newer packages automatically.

If you have questions or comments, please send them to the Cygwin
mailing list at: cygwin@cygwin.com .  I would appreciate if you would
use this mailing list rather than emailing me directly.  This includes
ideas and comments about the setup utility or Cygwin in general.

If you want to make a point or ask a question, the Cygwin mailing list
is the appropriate place.

              *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

If you want to unsubscribe from the cygwin-announce mailing list, look
at the "List-Unsubscribe: " tag in the email header of this message.
Send email to the address specified there.  It will be in the format:

cygwin-announce-unsubscribe-you=yourdomain.com@cygwin.com

Jason

--
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D  8784 1AFD E4CC ECF4 8EF6


From jan@jandecaluwe.com  Fri Mar  7 18:23:54 2003
From: jan@jandecaluwe.com (Jan Decaluwe)
Date: Fri, 07 Mar 2003 19:23:54 +0100
Subject: ANNOUNCE: MyHDL 0.1
Message-ID: <mailman.1047070861.23261.clpa-moderators@python.org>

I am happy to announce the initial public release of MyHDL, a
Python package for using Python as a hardware description language.

This may be of interest to:
- Pythoneers interested in applications of Python generators
- hardware designers interested in the wonders of Python

You can find it at http://jandecaluwe.com/Tools/MyHDL/Overview.html.

Release notes:

MyHDL 0.1
---------

MyHDL is a Python package for using Python as a hardware description
language. Popular hardware description languages, like Verilog and
VHDL, are compiled languages. MyHDL with Python can be viewed as a
"scripting language" counterpart of such languages. However, Python is
more accurately described as a very high level language (VHLL). MyHDL
users have access to the amazing power and elegance of Python for their
modeling work.

The key idea behind MyHDL is to use Python generators to model the
concurrency required in hardware descriptions. As generators are a
recent Python feature, MyHDL requires Python 2.2.2 or higher.

MyHDL 0.1 is the initial public release of the package. It can be used
to experiment with high level modeling, and with verification
techniques such as unit testing. But the primary goal is to generate
interest and to solicit feedback.

In a future release, MyHDL will hopefully be coupled to hardware
simulators for languages such as Verilog and VHDL. That would turn
Python into a powerful hardware verification language.

--
Jan Decaluwe - Resources bvba
Losbergenlaan 16, B-3010 Leuven, Belgium
mailto:jan@jandecaluwe.com
http://jandecaluwe.com


From pepvote@canada.com  Sat Mar  8 00:17:19 2003
From: pepvote@canada.com (Norman Petry)
Date: 07 Mar 2003 18:17:19 -0600
Subject: Reminder re: Complementary Vote on PEP Three-Zero-Eight
Message-ID: <mailman.1047087482.1862.clpa-moderators@python.org>

This message is to remind you that TOMORROW (Saturday) is the last day
to vote in the complementary, UNOFFICIAL vote on adding a ternary
operator to Python (PEP-308).  Response has been good so far, but the
more people that participate, the more useful the results will be. 
Please participate if you have the time.

A copy of the ballot, and instructions on how to vote are included
below, in case you missed the first announcement.

More information about this additional vote, and why it was organized
will be found here:

http://mail.python.org/pipermail/python-list/2003-March/151680.html


*****

IMPORTANT NOTE:

This is NOT a ballot for the "official" PEP-308 vote being run by
Raymond Hettinger.  It is for a different vote that is intended to
COMPLEMENT the results of the official vote, by using a different type
of ballot, and a different method of tallying the results (Condorcet's
Method), for those who may be interested.  If enough people choose to
participate, it will provide a high-quality source of additional
information about the preferences of the Python community regarding the
ternary operator.

This vote is NOT intended to compete with, or substitute for the
official vote.  Please participate in both votes if you have the time,
but BE SURE to vote in the official one if you care about the outcome of
PEP-308.  See the explanations in my posting to comp.lang.python two
days ago for more information about the reasons for this supplemental
vote on PEP-308 ("ANNOUNCE: Complementary VOTE re: PEP 308 Ternary
Proposal", Sun, 02 Mar 2003 17:44:33 -0600).
 

NOMINATIONS

The two-day nomination period for additional syntax proposals has now
ENDED.  No additional nominations were received, so the ballot is as
follows:


BALLOT

----------
XX  NO TERNARY
XX  t if C else f
XX  if C then t else f
XX  (if C: t else: f)
XX  if C: t else: f
XX  C ? t : f
XX  C ? t ! f
XX  cond(C, t, f)  
XX  C ?? t || f
XX  C then t else f
XX  t when C else f
XX  C ? t else f
XX  C -> t else f
XX  C -> (t, f)
XX  [t if C else f]
XX  ifelse C: t else f 
XX  select C: t else f 
XX  when C: t else f   
XX  case C: t else f   
XX  <if C then t else f>
XX  C and t else f
----------


HOW TO VOTE

Voting is a simple matter of RANKING the alternatives of interest by
replacing the 'XX' that precedes each option with a 2-digit number.  For
example, you would use '01' for your FAVOURITE (highest-ranked) option,
and greater numbers (02, 03,...) for lower-ranked alternatives.

You may RE-ORDER the options on the ballot.  It is often easier when
there are many options to reorder them manually from best to worst, and
then assign rankings.  Note though, that you must STILL assign a rank
number to each option, since it is always the NUMBER that determines the
rank, not the ordering.

You may assign the SAME RANK to multiple options if you consider them to
be equally good/bad.  Doing this is equivalent to abstaining from
participation in any decision between these equally-ranked alternatives.

To simplify voting, you may TRUNCATE your ballot by leaving certain
options UNRANKED (for any options you consider to be so bad and
unwinnable as to not be worth considering).  If you wish to do this,
either:
a) leave 'XX' in front of the unwanted option(s) in your submitted
ballot, rather than replacing it with a rank number, or
b) delete the line(s) of the ballot that contain the unwanted options.
You can also use a combination of both methods.  In either case, these
truncated options will be interpreted the same as if they had been
ranked EQUALLY, and LOWER than all explicitly ranked alternatives.  

While truncation and equal rankings provide convenience, ranking many
options (even those you dislike) is a good idea.  See the STRATEGY TIPS
section (below) for reasons why.

Note that the status quo option of "NO TERNARY" simply appears as one of
the available options, and every other proposed syntax appears as a
separate option on the ballot.  By placing "NO TERNARY" somewhere within
the middle of your ranking, you can express the desire to have a ternary
operator added to Python only if certain forms of syntax are used, and
reject alternatives that you dislike (while still expressing preferences
among these bad alternatives, in case one or more of them proves to be
winnable).  The status quo option can of course also be ranked first or
last, if you feel either that (a) no ternary is acceptable in any form,
or alternately, (b) should be added to the language at any cost.  

A sample completed ballot might look like:

----------
02  (if C: t else: f)
01  t if C else f
02  NO TERNARY
XX  if C then t else f
03  if C: t else: f
----------

Here, the voter's favourite option is "t if C else f".  The 4th option
is unranked, and could have instead been deleted to indicate the same
thing.  Surrounding lines of hyphens marking the beginning and end of
the ballot are appreciated for clarity, but not required.


SUBMITTING YOUR BALLOT

You may vote by submitting your email ballot to:

------------------
pepvote@canada.com
------------------

Your final vote must be received within 96 HOURS (4 days, approx.
Wed-Sat) of the time this message first appears on comp.lang.python
and/or comp.lang.python.announce for it to be counted in the final
result.

A CONFIRMATION message will be returned for each ballot that is
received, identifying any problems.  Unconfirmed ballots will not appear
in the results, so if you don't receive a reply within a few hours, you
may wish to send your ballot again (I'm confirming votes manually, so
the response will not be immediate).  

If you decide to CHANGE YOUR VOTE, just send a revised ballot containing
your new preferences.  The last confirmed ballot for each email address
will be the one that appears in the final results.


RESULTS

Results will be published on Sunday, March 9th, but NOT before the
voting period of the "official" vote has ended (Noon, EST).  Published
results will be sent to comp.lang.python and comp.lang.python.announce.

Results will include (among other things) a list containing each voter's
NAME, EMAIL ADDRESS (munged), and COMPLETED BALLOT to allow for
independent verification.  Therefore, if you do not want any or all of
this information about you made public, DO NOT VOTE!  Please refer to
the previous message announcing this vote for details about what types
of information will appear in the results.


STRATEGY TIPS

You may be unfamiliar with CONDORCET'S METHOD, the system of voting used
here (unless you happen to be a member of the Debian Project :-). 
Although completing a ranked ballot is technically very easy, if you
wish to know how to maximise the chances of getting the outcome you
want, you should read following information before completing your
ballot:

*****

1. Condorcet's method of counting ranked ballots is very different from
other systems (STV/AV/IRV, Borda, etc.) that also use a ranked ballot. 
Therefore, it is a bad idea to attempt to vote strategically based on
what you know (or think you know) about how those systems work.  The
best strategies for one method of voting will usually fail very badly
when applied in another, even if the form of the ballot is similar.

2. You should NOT assume that ranking any UNACCEPTABLE options will harm
the chances of electing your PREFERRED option(s).  Condorcet's method is
a system of pairwise voting, where the overall result is determined by
finding the majority winners of a series of two-way races between every
possible pair of alternatives.  Not ranking (truncating) some options,
or assigning the same rank to a group of options is therefore equivalent
to ABSTAINING from participation in any decision between those
equally-ranked alternatives.  Therefore, if the final choice in the
election is between two options, both of which you dislike -- but not
EQUALLY -- you may later regret not having participated in that
decision.

3. You should also NOT vote for what you believe to be an acceptable,
popular choice (the "lesser evil" compromise) ahead of your true
favourite(s), in the belief that this will somehow help to prevent the
election of a popular, disliked alternative (the "greater evil").  This
type of strategy is often necessary in plurality ("first-past-the-post")
voting, but is ineffective and unnecessary with Condorcet's method. 
Condorcet's method finds the best compromise automatically, if one is
needed, so doing this will simply harm the chances of electing your true
favourite.  See http://www.electionmethods.org/Condorcet.htm for a
detailed explanation of this.

*******************************************************
With CONDORCET'S METHOD, you will maximise the power and effectiveness
of your ballot by providing a COMPLETE and SINCERE expression of your
true preferences.  You should only rank options equally if you genuinely
consider them to be equally good (or bad).
*******************************************************

--
Norman Petry



From mail@heikokoehler.de  Sat Mar  8 18:26:25 2003
From: mail@heikokoehler.de (Heiko =?ISO-8859-15?Q?K=F6hler?=)
Date: Sat, 08 Mar 2003 19:26:25 +0100
Subject: New scriptable Scintilla and QT based Text Editor
Message-ID: <mailman.1047245114.17688.clpa-moderators@python.org>

I have just released 0.1.2 of CUTE. The CUTE User-friendly Text Editor is a
scintilla and QT based code editor, which can be extented using the python
scripting language. In addition CUTE has a command box for vi-like commands.
It is available for X11/Linux and should be portable to other platforms. 
In addition CUTE has a command box for vi-like commands.
The project page of CUTE is http://cute.sourceforge.net.
It has also a page at sourceforge.net: http://sourceforge.net/projects/cute


From npetry@accesscomm.ca  Sun Mar  9 18:45:13 2003
From: npetry@accesscomm.ca (Norman Petry)
Date: 09 Mar 2003 12:45:13 -0600
Subject: BALLOTS: Complementary PEP308 Ternary Vote
Message-ID: <mailman.1047245114.17718.clpa-moderators@python.org>

IMPORTANT NOTE: 

The ballot information contained in this message is for the
Complementary, UNOFFICIAL vote on the issue of adding a ternary operator
to Python (PEP308).  It is NOT the data that will be used to determine
the OFFICIAL results, which are being tabulated by Raymond Hettinger.

This COMPLEMENTARY vote uses a different type of ballot, as well as a
different method of tallying them (Condorcet's Method) which should
provide additional insight into the preferences of the Python community
regarding PEP308.  See: 

http://mail.python.org/pipermail/python-list/2003-March/151680.html

for additional information about this vote.

If you voted in this complementary vote, please check the list below to
determine that your ballot was counted correctly. 

Results from this vote vote will be posted in a followup message,
entitled: "RESULTS: Complementary PEP308 Ternary Vote"

-- 
Norman Petry 

OPTIONS
=======

01 = NO TERNARY
02 = t if C else f
03 = if C then t else f
04 = (if C: t else: f)
05 = if C: t else: f
06 = C ? t : f
07 = C ? t ! f
08 = cond(C, t, f)
09 = C ?? t || f
10 = C then t else f
11 = t when C else f
12 = C ? t else f
13 = C -> t else f
14 = C -> (t, f)
15 = [t if C else f]
16 = ifelse C: t else f
17 = select C: t else f
18 = when C: t else f
19 = case C: t else f
20 = <if C then t else f>
21 = C and t else f


BALLOTS
=======

01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 "Voter Name" <email address>
==============================================================
05|11|11|02|03|01|12|10|04|12|12|12|13|13|14|08|09|06|07|14|15 "" <PYgs@qfs.de>
03|01|XX|XX|XX|XX|XX|XX|XX|XX|02|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX "" <gyromaPYgnetic@excite.com>
01|09|06|15|05|03|15|25|25|25|13|20|20|20|99|99|99|99|99|99|80 "" <hoPYward@eegsoftware.com>
11|20|04|01|02|03|14|15|16|07|08|09|17|18|19|13|10|05|06|12|21 "" <mstoPYne@ugcs.caltech.edu>
02|01|09|13|14|04|06|10|05|08|03|07|11|12|19|17|18|15|16|21|20 "" <pPYaul@svensson.org>
03|XX|XX|01|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|02|XX "" <prPYen_lexen@fastmail.fm>
02|02|02|03|03|02|03|03|03|01|01|03|03|03|03|03|03|03|03|03|03 "alan haffner" <yaiPYpa@yahoo.com>
01|13|04|02|09|XX|XX|XX|XX|08|12|XX|XX|XX|03|14|06|05|07|10|11 "Alex Martelli" <aleaxPY@aleax.it>
01|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX "Amos Latteier" <amPYos@aracnet.com>
01|06|06|02|08|10|10|07|10|04|06|09|09|10|03|05|05|05|05|02|04 "Anders Hammarquist" <iPYko@cd.chalmers.se>
01|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX "Andrew Dalke" <adaPYlke@mindspring.com>
01|02|03|XX|XX|04|08|09|XX|07|XX|06|XX|XX|XX|XX|XX|05|XX|XX|XX "Andrew Hamilton" <aPYnd_hamilton@yahoo.com>
05|06|06|06|08|02|01|08|02|06|07|04|04|03|06|06|06|07|06|06|06 "Andrew Reid" <andrew.PYreid@nist.gov>
07|05|08|02|03|01|08|08|08|08|06|08|08|08|08|08|08|08|08|04|08 "Andrew Sterian" <steriPYana@claymore.engineer.gvsu.edu>
06|01|09|10|11|04|02|12|08|13|03|05|19|20|14|15|16|18|17|21|07 "Barry A. Warsaw" <baPYrry@python.org>
02|12|09|03|02|02|05|14|04|08|13|06|05|07|13|11|11|11|11|10|01 "Beni Cherniavsky" <cbenPY@techunix.technion.ac.il>
01|99|99|99|03|10|10|99|10|99|99|99|99|99|99|99|99|99|99|99|99 "Berthold =?iso-8859-1?q?H=F6llmann?=" <bhoPYel@web.de>
11|12|04|03|05|01|06|13|02|02|12|04|07|08|12|09|09|09|09|06|10 "Carl Banks" <pep308PY@aerojockey.com>
15|01|02|05|06|07|09|16|10|03|04|11|13|18|20|12|14|08|17|21|19 "Chermside, Michael" <mchPYermside@ingdirect.com>
09|01|02|04|05|06|14|07|21|11|08|13|10|03|19|15|16|12|17|20|18 "Colin Dewey" <cndeweyPY@yahoo.com>
06|99|07|01|02|03|99|99|08|99|99|04|99|09|99|99|99|99|10|07|05 "David Schnepper" <davidPYsch@verity.com>
05|51|21|01|02|10|11|03|12|22|52|13|98|99|53|31|32|33|34|41|04 "David Stegbauer" <dsPYtegbauer@post.cz>
21|16|03|02|01|12|13|19|14|04|17|15|10|11|18|08|07|05|06|09|20 "Davide Di Blasi" <davide.di-blasiPY@st.com>
04|XX|03|XX|XX|01|XX|XX|XX|02|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX "Denis S. Otkidach" <PYods@strana.ru>
01|XX|01|01|02|XX|XX|02|XX|XX|XX|XX|02|01|XX|XX|XX|02|XX|02|XX "Dennis Lee Bieber" <wlfrPYaed@ix.netcom.com>
03|01|02|XX|XX|XX|XX|XX|XX|05|04|XX|XX|XX|06|XX|XX|XX|XX|XX|XX "Donnal Walter" <dPYonnal@donnal.net>
XX|XX|01|04|03|XX|XX|02|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX "Doug Henderson" <djPYhender@telusplanet.net>
01|XX|XX|XX|02|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX "douglas savitsky" <dsavitskPY@mail.e-coli.net>
XX|01|03|02|XX|XX|XX|XX|XX|04|05|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX "dwelch" <dwelPYch91@attbi.com>
11|09|01|03|02|05|06|08|07|04|10|12|18|19|20|13|14|15|16|17|21 "Egbert Bouwman" <egbert.lPYist@hccnet.nl>
16|17|05|04|03|01|02|19|10|08|20|06|07|09|21|13|18|12|14|11|15 "Elron A. Yellin" <PYelronayellin@attbi.com>
03|01|05|09|08|15|17|10|18|11|02|14|13|16|04|19|20|07|21|06|12 "Eric Pettersen" <pPYett@cgl.ucsf.edu>
06|04|03|01|02|15|16|21|17|08|09|20|18|19|07|10|11|12|13|05|14 "Evan Simpson" <evPYan@4-am.com>
05|01|XX|02|04|03|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX "Felix Beer" <PYf.beer@indec.at>
13|11|03|02|04|01|XX|10|09|07|12|XX|XX|XX|XX|XX|XX|05|06|XX|08 "Fernando Perez" <fpPYerez@colorado.edu>
08|05|00|02|01|03|09|17|10|16|04|11|12|20|06|13|14|07|15|19|18 "Gareth McCaughan" <gareth.mccaughanPY@pobox.com>
01|01|04|XX|XX|03|03|XX|02|04|02|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX "Geoff Gerrietts" <gePYoff@homegain.com>
04|03|01|08|03|99|99|99|99|08|08|99|99|99|99|99|99|08|08|99|99 "george young" <PYgry@ll.mit.edu>
02|01|05|09|10|11|12|XX|14|03|06|13|04|08|XX|XX|XX|XX|XX|XX|07 "Gerd Woetzel" <gerd.PYwoetzel@fit.fraunhofer.de>
XX|99|10|01|09|08|08|07|08|10|99|03|08|20|99|XX|XX|XX|XX|02|XX "Gerhard Kirchmann" <gerhaPYrd1.kirchmann@nexgo.de>
02|01|07|04|04|07|07|05|07|06|06|07|07|07|01|07|05|03|05|07|06 "Giovanni Bajo" <giovPYannibajo@libero.it>
01|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX "Gordon Williams" <g_wPYill@cyberus.ca>
01|02|XX|XX|XX|XX|XX|XX|XX|XX|04|XX|XX|XX|03|XX|XX|XX|XX|XX|XX "Greg Krohn" <PYgreg@capra.us>
05|04|02|02|02|01|02|06|02|02|04|02|02|06|04|03|03|03|03|02|03 "Greg McFarlane" <PYgregm@iname.com>
01|XX|XX|XX|10|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX "Guido Goldstein" <pepvote308PY@a-nugget.de>
11|04|03|09|08|14|16|17|15|05|01|13|18|19|12|20|06|02|07|21|10 "Harvey Thomas" <hsPYt@empolis.co.uk>
20|03|04|16|14|11|06|19|05|07|02|01|10|15|08|13|18|12|17|21|09 "Ian Bicking" <ianbPY@colorstudy.com>
03|04|02|06|XX|07|XX|XX|XX|01|05|08|XX|XX|XX|XX|XX|XX|XX|XX|XX "Ian Douglas Bollinger" <escovPYan@myrealbox.com>
05|12|01|02|02|04|06|16|06|03|13|06|06|11|15|08|09|04|09|10|14 "Jakob Schiotz" <sPYchiotz@fysik.dtu.dk>
07|XX|03|01|02|XX|XX|XX|XX|08|XX|XX|XX|XX|XX|06|04|XX|05|XX|XX "Jens =?ISO-8859-1?Q?J=F8rgen?= Mortensen" <jjPYm@tiscali.dk>
XX|XX|01|04|03|02|XX|XX|XX|05|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX "Jim Fulton" <jimPY@zope.com>
03|XX|02|XX|XX|XX|XX|01|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX "john grosspietsch" <jPYohnkg@earthlink.net>
04|02|05|08|09|03|17|18|10|07|01|11|12|13|20|14|06|15|16|20|19 "John Hazen" <pPYython-list@hazen.net>
14|11|03|05|02|01|06|21|07|04|19|08|09|10|20|16|18|15|17|12|13 "John J Smith" <jPYohnjsmith@rediffmail.com>
04|01|03|06|05|07|12|10|08|11|02|14|13|09|18|17|16|15|16|18|18 "John Williams" <PYjrw@pobox.com>
01|03|02|03|03|03|03|03|03|02|03|03|03|03|03|03|03|03|03|03|03 "Jp Calderone" <exarkunPY@intarweb.us>
02|XX|01|XX|XX|03|XX|XX|03|01|XX|XX|XX|03|XX|XX|XX|XX|XX|XX|03 "Kirill Simonov" <kirill_simonPYov@mail.ru>
XX|XX|XX|XX|02|01|03|04|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX "Korolkov Dmitry" <korolkoPYv@lcard.ru>
03|02|02|XX|03|01|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX "L&E Druker" <ledrukerPY@rogers.com>
03|04|04|01|04|04|04|04|04|02|04|04|04|04|04|04|04|04|04|04|04 "Luis P Caamano" <lcaamanoPY@mindspring.com>
XX|XX|XX|XX|02|01|XX|XX|03|XX|XX|XX|XX|04|XX|XX|XX|XX|XX|XX|XX "Lutz Schroeer" <lschPYroeer@elektroelch.de>
01|20|04|07|06|05|17|02|18|03|21|14|15|16|19|12|13|09|11|10|08 "Magnus Lycka" <maPYgnus@thinkware.se>
08|XX|06|02|05|03|04|XX|01|XX|XX|07|XX|XX|XX|XX|XX|XX|XX|XX|XX "Manuel M. Garcia" <mPYgarcia@cole-switches.com>
01|05|06|02|04|XX|XX|XX|XX|XX|08|XX|XX|XX|XX|XX|XX|03|07|XX|XX "Matthew Dixon Cowles" <mattPY@mondoinfo.com>
XX|XX|XX|XX|XX|01|03|XX|02|XX|XX|05|06|XX|XX|XX|XX|04|XX|XX|XX "Michael Gleicher" <glePYicher@cs.wisc.edu>
02|99|99|01|90|95|95|99|05|99|99|98|99|99|99|99|99|99|99|99|99 "Mike Howard" <mikPYe@clove.com>
03|04|01|02|03|XX|XX|XX|XX|05|05|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX "Mike Rovner" <PYmrovner@hotmail.com>
06|19|01|03|04|02|09|05|10|07|20|08|11|12|21|13|14|15|16|17|18 "Nick Coghlan" <ncoghPYlan@email.com>
01|XX|XX|02|03|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|04|XX|XX|XX|XX "Nick Efford" <ndePY@comp.leeds.ac.uk>
02|01|17|03|06|13|15|05|16|19|04|08|09|14|20|12|11|07|10|18|21 "Norman Petry" <npePYtry@accesscomm.ca>
09|10|11|01|12|02|03|21|04|13|14|06|07|08|05|15|16|17|18|20|19 "Oleg Broytmann" <pPYhd@phd.pp.ru>
04|03|05|01|05|02|99|99|99|06|06|05|06|99|99|06|06|06|06|99|06 "Oliver Schaefer" <schaPYeferffm@gmx.de>
16|05|01|04|02|06|09|12|14|03|14|11|08|07|17|15|13|13|13|17|10 "Parzival Herzog" <PYparz@shaw.ca>
01|02|XX|XX|XX|XX|XX|08|XX|XX|11|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX "Paul Paterson" <paulpatersPYon@houston.rr.com>
01|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX "Paul Sidorsky" <pauPYlsid@shaw.ca>
04|05|03|01|02|06|06|05|XX|05|XX|05|06|06|XX|06|XX|XX|XX|XX|XX "Peter Maxwell" <maxwePYll@biolateral.com.au>
07|XX|03|02|02|01|05|04|05|05|XX|05|06|06|XX|07|07|07|07|02|XX "phil hunt" <philhPY@cabalamat.org>
08|16|03|04|09|11|01|07|02|06|17|05|21|20|18|14|15|12|13|19|10 "Piers Lauder" <pierPYs@cs.su.oz.au>
01|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX "Rafal Smotrzyk" <rsmotrPYzyk@mikroplan.com.pl>
08|XX|01|04|03|02|XX|XX|XX|06|XX|07|XX|XX|XX|XX|XX|XX|XX|XX|05 "Ralph Corderoy" <PYralph@inputplus.co.uk>
06|19|02|01|07|14|15|10|16|11|21|17|12|13|20|03|04|09|05|08|18 "Randolph Brown" <rgbPY@panix.com>
01|04|XX|02|03|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX "Richard Emslie" <rxPYe@ukshells.co.uk>
01|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX "Richard Jones" <richardjPYones@optushome.com.au>
14|18|10|01|09|03|04|13|05|06|17|12|11|16|07|08|08|08|08|02|15 "Robin Munn" <rmPYunn@pobox.com>
01|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX "Rod Haper" <rhaPYper@houston.rr.com>
XX|02|01|05|04|03|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX "Russell E. Owen" <rPYowen@cesmail.net>
04|02|03|XX|XX|XX|XX|XX|XX|XX|01|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX "Sean Ross" <seanPYdavidross@hotmail.com>
02|03|97|97|03|99|99|01|99|06|04|99|99|99|99|98|98|05|98|99|03 "Shane Holloway (IEEE)" <PYshane.holloway@ieee.org>
01|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX "Stephan Deibel" <sdeibPYel@wingide.com>
15|12|04|08|08|07|02|14|01|05|12|03|06|06|13|09|09|09|09|10|11 "Stephen A. Langer" <stePYphen.langer@nist.gov>
01|15|04|02|03|06|07|21|09|10|16|08|13|14|17|18|19|11|12|20|05 "Ted Horst" <tedPY.horst@ubsw.com>
07|05|XX|XX|XX|03|04|XX|XX|01|06|XX|XX|XX|XX|XX|XX|XX|XX|XX|02 "Terry Reedy" <tjrePYedy@udel.edu>
01|XX|03|02|03|02|03|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|03|XX "Thomas Wouters" <thomPYas@xs4all.net>
01|02|XX|XX|XX|XX|XX|XX|XX|03|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX "Tim Evans" <t.evansPY@paradise.net.nz>
XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX "Tom Culliton" <culPYliton@io.com>
01|02|XX|03|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX "Tony J Ibbs (Tibs)" <PYtony@lsl.co.uk>
09|06|06|01|04|03|05|08|05|06|06|07|07|03|04|06|06|06|06|02|06 "Treutwein Guido" <guido.treutweinPY@siemens.com>
XX|XX|XX|XX|XX|01|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX "Vladimir Pastukhov" <PYvlpast@mail.ru>
01|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX "Walter Moreira" <walterPYm@parque.homelinux.net>
20|01|04|09|08|10|11|19|03|05|02|06|07|17|18|12|15|13|14|21|16 "Werner Schiendl" <PYws-news@gmx.at>
XX|03|XX|02|XX|XX|XX|XX|XX|XX|XX|XX|XX|XX|01|XX|XX|XX|XX|XX|XX "William Dode" <wPYilk@flibuste.net>
==============================================================
Remove "PY" from voter email addresses before sending mail.
Total Ballots: 101





From npetry@accesscomm.ca  Sun Mar  9 19:02:52 2003
From: npetry@accesscomm.ca (Norman Petry)
Date: 09 Mar 2003 13:02:52 -0600
Subject: RESULTS: Complementary PEP308 Ternary Vote
Message-ID: <mailman.1047245115.17762.clpa-moderators@python.org>

IMPORTANT NOTE: 

The results shown below are for the complementary, UNOFFICIAL vote on
the issue of adding a ternary operator to Python (PEP308).  These
results will probably be a bit different from the OFFICIAL results,
which are being tabulated by Raymond Hettinger using a different
technique and a different set of ballots.  Both sets of results are
non-binding, and intended only to advise the BDFL about the Python
community's wishes regarding the implementation of PEP308.  Hopefully,
this supplemental vote will provide Guido van Rossum with additional
insight into the wishes of Python users. See: 

http://mail.python.org/pipermail/python-list/2003-March/151680.html

for additional information about this vote.

This COMPLEMENTARY vote used a ranked ballot and Condorcet's method to
determine a winner.  For background information about how this method
works, see:

http://www.electionmethods.org/CondorcetEx.htm

The results shown below are based on 101 ballots received over a one
week period (March 3-9).  The ballots themselves may be viewed here:

http://mail.python.org/pipermail/python-list/2003-March/152304.html


VOTING SOFTWARE
===============

GNU GPL-licensed voting software written in Python is available to
verify these results.  It could also be used again in future votes if
the Python community wishes to use Condorcet's method to advise the BDFL
on other PEPs.  You can download a package containing this software as
well as all the data used for this vote from:

http://24.72.22.210/pepvote.tar.gz

This software was written and tested using Python 2.2 running on Red Hat
Linux 8.0.  Use on other platforms may require some adaptation.


SINGLE WINNER
=============

The Condorcet Winner is: "NO TERNARY".


SOCIAL RANKING (Tideman)
========================

 1. NO TERNARY
 2. if C then t else f
 3. (if C: t else: f)
 4. C ? t : f
 5. if C: t else: f
 6. t if C else f
 7. C then t else f
 8. t when C else f
 9. C ? t ! f
10. C ?? t || f
11. C ? t else f
12. when C: t else f
13. C -> t else f
14. case C: t else f
15. ifelse C: t else f
16. select C: t else f
17. cond(C, t, f)
18. C -> (t, f)
19. C and t else f
20. <if C then t else f>
21. [t if C else f]

Kemeny Score: 9681


PAIRWISE COMPARISONS
====================

Option "NO TERNARY":
   beats option "if C then t else f" [50 - 43]
   beats option "(if C: t else: f)" [50 - 45]
   beats option "C ? t : f" [54 - 41]
   beats option "if C: t else: f" [55 - 38]
   beats option "t if C else f" [56 - 36]
   beats option "C then t else f" [64 - 29]
   beats option "t when C else f" [67 - 25]
   beats option "C ? t ! f" [70 - 23]
   beats option "C ?? t || f" [70 - 23]
   beats option "C ? t else f" [69 - 23]
   beats option "when C: t else f" [73 - 17]
   beats option "C -> t else f" [75 - 17]
   beats option "case C: t else f" [74 - 15]
   beats option "ifelse C: t else f" [76 - 13]
   beats option "select C: t else f" [75 - 14]
   beats option "cond(C, t, f)" [74 - 19]
   beats option "C -> (t, f)" [76 - 15]
   beats option "C and t else f" [73 - 17]
   beats option "<if C then t else f>" [78 - 13]
   beats option "[t if C else f]" [80 - 12]

Option "if C then t else f":
   beats option "(if C: t else: f)" [38 - 37]
   beats option "C ? t : f" [41 - 36]
   beats option "if C: t else: f" [45 - 32]
   beats option "t if C else f" [43 - 31]
   beats option "C then t else f" [51 - 15]
   beats option "t when C else f" [54 - 19]
   beats option "C ? t ! f" [52 - 20]
   beats option "C ?? t || f" [51 - 21]
   beats option "C ? t else f" [55 - 13]
   beats option "when C: t else f" [61 - 9]
   beats option "C -> t else f" [62 - 7]
   beats option "case C: t else f" [63 - 5]
   beats option "ifelse C: t else f" [63 - 4]
   beats option "select C: t else f" [63 - 6]
   beats option "cond(C, t, f)" [62 - 10]
   beats option "C -> (t, f)" [63 - 6]
   beats option "C and t else f" [61 - 8]
   beats option "<if C then t else f>" [60 - 7]
   beats option "[t if C else f]" [62 - 9]

Option "(if C: t else: f)":
   beats option "C ? t : f" [47 - 33]
   beats option "if C: t else: f" [44 - 26]
   beats option "t if C else f" [47 - 32]
   beats option "C then t else f" [52 - 23]
   beats option "t when C else f" [55 - 21]
   beats option "C ? t ! f" [60 - 13]
   beats option "C ?? t || f" [59 - 14]
   beats option "C ? t else f" [62 - 8]
   beats option "when C: t else f" [63 - 7]
   beats option "C -> t else f" [62 - 7]
   beats option "case C: t else f" [66 - 1]
   beats option "ifelse C: t else f" [67 - 1]
   beats option "select C: t else f" [66 - 2]
   beats option "cond(C, t, f)" [65 - 8]
   beats option "C -> (t, f)" [62 - 8]
   beats option "C and t else f" [63 - 7]
   beats option "<if C then t else f>" [64 - 1]
   beats option "[t if C else f]" [64 - 6]

Option "C ? t : f":
   beats option "if C: t else: f" [40 - 37]
   beats option "t if C else f" [43 - 37]
   beats option "C then t else f" [44 - 32]
   beats option "t when C else f" [49 - 28]
   beats option "C ? t ! f" [54 - 5]
   beats option "C ?? t || f" [53 - 7]
   beats option "C ? t else f" [55 - 10]
   beats option "when C: t else f" [57 - 13]
   beats option "C -> t else f" [54 - 10]
   beats option "case C: t else f" [59 - 12]
   beats option "ifelse C: t else f" [59 - 8]
   beats option "select C: t else f" [59 - 11]
   beats option "cond(C, t, f)" [56 - 15]
   beats option "C -> (t, f)" [56 - 6]
   beats option "C and t else f" [53 - 14]
   beats option "<if C then t else f>" [57 - 11]
   beats option "[t if C else f]" [60 - 10]

Option "if C: t else: f":
   beats option "t if C else f" [47 - 34]
   beats option "C then t else f" [53 - 27]
   beats option "t when C else f" [56 - 23]
   beats option "C ? t ! f" [56 - 15]
   beats option "C ?? t || f" [55 - 16]
   beats option "C ? t else f" [57 - 13]
   beats option "when C: t else f" [59 - 11]
   beats option "C -> t else f" [59 - 9]
   beats option "case C: t else f" [63 - 6]
   beats option "ifelse C: t else f" [64 - 5]
   beats option "select C: t else f" [62 - 7]
   beats option "cond(C, t, f)" [59 - 11]
   beats option "C -> (t, f)" [61 - 9]
   beats option "C and t else f" [62 - 8]
   beats option "<if C then t else f>" [59 - 7]
   beats option "[t if C else f]" [60 - 11]

Option "t if C else f":
   beats option "C then t else f" [39 - 33]
   beats option "t when C else f" [52 - 9]
   beats option "C ? t ! f" [45 - 29]
   beats option "C ?? t || f" [44 - 31]
   beats option "C ? t else f" [46 - 26]
   beats option "when C: t else f" [45 - 24]
   beats option "C -> t else f" [50 - 20]
   beats option "case C: t else f" [46 - 22]
   beats option "ifelse C: t else f" [49 - 18]
   beats option "select C: t else f" [49 - 19]
   beats option "cond(C, t, f)" [54 - 17]
   beats option "C -> (t, f)" [50 - 22]
   beats option "C and t else f" [48 - 19]
   beats option "<if C then t else f>" [48 - 23]
   beats option "[t if C else f]" [54 - 8]

Option "C then t else f":
   beats option "t when C else f" [41 - 21]
   beats option "C ? t ! f" [42 - 24]
   beats option "C ?? t || f" [40 - 25]
   beats option "C ? t else f" [42 - 21]
   beats option "when C: t else f" [48 - 15]
   beats option "C -> t else f" [52 - 11]
   beats option "case C: t else f" [50 - 11]
   beats option "ifelse C: t else f" [55 - 5]
   beats option "select C: t else f" [52 - 9]
   beats option "cond(C, t, f)" [47 - 19]
   beats option "C -> (t, f)" [55 - 11]
   beats option "C and t else f" [52 - 7]
   beats option "<if C then t else f>" [52 - 14]
   beats option "[t if C else f]" [54 - 10]

Option "t when C else f":
   beats option "C ? t ! f" [34 - 32]
   beats option "C ?? t || f" [34 - 30]
   beats option "C ? t else f" [36 - 29]
   beats option "when C: t else f" [31 - 27]
   beats option "C -> t else f" [39 - 22]
   beats option "case C: t else f" [31 - 27]
   beats option "ifelse C: t else f" [39 - 20]
   beats option "select C: t else f" [36 - 23]
   beats option "cond(C, t, f)" [42 - 23]
   beats option "C -> (t, f)" [40 - 24]
   beats option "C and t else f" [35 - 23]
   beats option "<if C then t else f>" [38 - 25]
   beats option "[t if C else f]" [43 - 12]

Option "C ? t ! f":
   beats option "C ?? t || f" [29 - 18]
   beats option "C ? t else f" [31 - 19]
   beats option "when C: t else f" [34 - 24]
   beats option "C -> t else f" [34 - 13]
   beats option "case C: t else f" [40 - 19]
   beats option "ifelse C: t else f" [40 - 13]
   beats option "select C: t else f" [40 - 16]
   beats option "cond(C, t, f)" [37 - 20]
   beats option "C -> (t, f)" [37 - 15]
   beats option "C and t else f" [40 - 18]
   beats option "<if C then t else f>" [36 - 16]
   beats option "[t if C else f]" [44 - 11]

Option "C ?? t || f":
   beats option "C ? t else f" [29 - 22]
   beats option "when C: t else f" [34 - 23]
   beats option "C -> t else f" [35 - 14]
   beats option "case C: t else f" [38 - 18]
   beats option "ifelse C: t else f" [41 - 13]
   beats option "select C: t else f" [38 - 17]
   beats option "cond(C, t, f)" [36 - 21]
   beats option "C -> (t, f)" [36 - 13]
   beats option "C and t else f" [34 - 20]
   beats option "<if C then t else f>" [35 - 18]
   beats option "[t if C else f]" [42 - 12]

Option "C ? t else f":
   beats option "when C: t else f" [31 - 25]
   beats option "C -> t else f" [33 - 11]
   beats option "case C: t else f" [39 - 17]
   beats option "ifelse C: t else f" [41 - 11]
   beats option "select C: t else f" [39 - 15]
   beats option "cond(C, t, f)" [36 - 20]
   beats option "C -> (t, f)" [39 - 12]
   beats option "C and t else f" [37 - 18]
   beats option "<if C then t else f>" [38 - 15]
   beats option "[t if C else f]" [41 - 13]

Option "when C: t else f":
   beats option "C -> t else f" [28 - 21]
   beats option "case C: t else f" [33 - 5]
   beats option "ifelse C: t else f" [28 - 12]
   beats option "select C: t else f" [28 - 11]
   beats option "cond(C, t, f)" [33 - 20]
   beats option "C -> (t, f)" [31 - 23]
   beats option "C and t else f" [32 - 18]
   beats option "<if C then t else f>" [33 - 18]
   beats option "[t if C else f]" [35 - 16]

Option "C -> t else f":
   beats option "case C: t else f" [28 - 23]
   beats option "ifelse C: t else f" [28 - 17]
   beats option "select C: t else f" [28 - 20]
   loses to option "cond(C, t, f)" [24 - 27]
   beats option "C -> (t, f)" [32 - 10]
   beats option "C and t else f" [31 - 20]
   beats option "<if C then t else f>" [27 - 20]
   beats option "[t if C else f]" [32 - 17]

Option "case C: t else f":
   ties option "ifelse C: t else f" [18 - 18]
   ties option "select C: t else f" [16 - 16]
   beats option "cond(C, t, f)" [30 - 24]
   beats option "C -> (t, f)" [28 - 25]
   beats option "C and t else f" [29 - 18]
   beats option "<if C then t else f>" [32 - 18]
   beats option "[t if C else f]" [34 - 15]

Option "ifelse C: t else f":
   beats option "select C: t else f" [22 - 11]
   ties option "cond(C, t, f)" [26 - 26]
   loses to option "C -> (t, f)" [23 - 25]
   beats option "C and t else f" [24 - 22]
   beats option "<if C then t else f>" [27 - 20]
   beats option "[t if C else f]" [29 - 17]

Option "select C: t else f":
   beats option "cond(C, t, f)" [28 - 24]
   beats option "C -> (t, f)" [26 - 25]
   beats option "C and t else f" [26 - 20]
   beats option "<if C then t else f>" [30 - 18]
   beats option "[t if C else f]" [30 - 16]

Option "cond(C, t, f)":
   beats option "C -> (t, f)" [28 - 24]
   beats option "C and t else f" [30 - 26]
   beats option "<if C then t else f>" [28 - 25]
   beats option "[t if C else f]" [29 - 24]

Option "C -> (t, f)":
   beats option "C and t else f" [27 - 24]
   beats option "<if C then t else f>" [26 - 23]
   beats option "[t if C else f]" [33 - 17]

Option "C and t else f":
   beats option "<if C then t else f>" [26 - 25]
   beats option "[t if C else f]" [29 - 20]

Option "<if C then t else f>":
   beats option "[t if C else f]" [26 - 17]

-- 
Norman Petry 




From and@doxdesk.com  Mon Mar 10 12:49:13 2003
From: and@doxdesk.com (Andrew Clover)
Date: Mon, 10 Mar 2003 12:49:13 +0000
Subject: Spec: Python XML templating language (PXTL)
In-Reply-To: <20030310100334.GA29341@doxdesk.com>
References: <20030309212458.17355.7923.Mailman@mail.python.org> <20030310100334.GA29341@doxdesk.com>
Message-ID: <mailman.1047306183.14004.clpa-moderators@python.org>

PXTL is a specification for a templating format mixing XML-based markup
languages with Python code. It is especially suitable for use in a web
application's page output stage.

*Another* web templating system? Yes, I'm afraid so. PXTL does have a few
features which are (as far as I know) unique, though:

  - it's a pure-XML format, which should make syntax and nesting errors
    very easy to debug (especially with a syntax-colouring, well-formedness
    checking text editor);
  - output can automatically be translated into legacy (non-XML) HTML or
    non-tag-based formats;
  - a number of XML processing instructions for including content in
    various common escaping formats;
  - elements from a separate namespace for flow-control (if, for, def, etc.),
    to allow a Python code hierarchy and XML markup hierarchy to be mixed
    cleanly.

I'm pleased to announce the second draft of the PXTL specification, and I'd
appreciate any feedback on it from web and XML authors (in particular those
familiar with XHTML) either by mail or to c.l.py.

  http://www.doxdesk.com/pxtl/

A reference implementation will be made available (under some manner of
open-source licence) some time in the next few months, taking into account
any comments received.

cheers,

-- 
Andrew Clover
mailto:and@doxdesk.com
http://www.doxdesk.com/


From jason@tishler.net  Mon Mar 10 14:09:06 2003
From: jason@tishler.net (Jason Tishler)
Date: Mon, 10 Mar 2003 09:09:06 -0500
Subject: Updated Cygwin Package: python-2.2.2-7
Message-ID: <mailman.1047306184.14015.clpa-moderators@python.org>

New News:
=== ====
I have updated the version of Python to 2.2.2-7.  The tarballs should be
available on a Cygwin mirror near you shortly.

On Thu, Mar 06, 2003 at 05:18:07PM -0500, Jason Tishler wrote:
> Otherwise, this package should be identical to the previous one.

I knew when I wrote the above I would regret it. :,)

The only purpose of this release is to fix a build issue that prevented
the _tkinter module from being included in the python-2.2.2-6 package.
I apologize for any inconvenience.

Old News:
=== ====
Python is an interpreted, interactive, object-oriented programming
language.  If interested, see the Python web site for more details:
                                                                   
    http://www.python.org/                                         

Please read the README file:
                            
    /usr/doc/Cygwin/python-2.2.2.README

since it covers requirements, installation, known issues, etc.

To update your installation, click on the "Install Cygwin now" link on
the http://cygwin.com/ web page.  This downloads setup.exe to your
system.  Then, run setup and answer all of the questions.

Note that we have recently stopped downloads from sources.redhat.com
(aka cygwin.com) due to bandwidth limitations.  This means that you will
need to find a mirror which has this update.

In the US,
ftp://mirrors.rcn.net/mirrors/sources.redhat.com/cygwin/
is a reliable high bandwidth connection.

In Germany,
ftp://ftp.uni-erlangen.de/pub/pc/gnuwin32/cygwin/mirrors/cygnus/
is usually pretty good.

In the UK,
http://programming.ccp14.ac.uk/ftp-mirror/programming/cygwin/pub/cygwin/
is usually up-to-date within 48 hours.

If one of the above doesn't have the latest version of this package
then you can either wait for the site to be updated or find another
mirror.

The setup.exe program will figure out what needs to be updated on your
system and will install newer packages automatically.

If you have questions or comments, please send them to the Cygwin
mailing list at: cygwin@cygwin.com .  I would appreciate if you would
use this mailing list rather than emailing me directly.  This includes
ideas and comments about the setup utility or Cygwin in general.

If you want to make a point or ask a question, the Cygwin mailing list
is the appropriate place.

              *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

If you want to unsubscribe from the cygwin-announce mailing list, look
at the "List-Unsubscribe: " tag in the email header of this message.
Send email to the address specified there.  It will be in the format:

cygwin-announce-unsubscribe-you=yourdomain.com@cygwin.com

Jason

--
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D  8784 1AFD E4CC ECF4 8EF6


From peter@engcorp.com  Mon Mar 10 16:16:48 2003
From: peter@engcorp.com (Peter Hansen)
Date: Mon, 10 Mar 2003 11:16:48 -0500
Subject: Toronto-area Python/Zope user group, Tuesday March 25, 8-10pm
Message-ID: <mailman.1047337742.7582.clpa-moderators@python.org>

This is to announce the next PyGTA (Toronto and area
Python/Zope User Group) meeting, which will be held
Tuesday, March 25, 2003.  (Apologies for making this 
so close to PyCon DC 2003 (http://www.python.org/pycon/)
but it was again the only day free.)

The location is the same as the last few times, but back
in room 23 again instead of the auditorium.

Further details will as usual be posted to our wiki
page at http://web.engcorp.com/pygta/wiki/NextMeeting .

-Peter and Ian, meeting organizers


From pep308vote@hotmail.com  Mon Mar 10 20:11:50 2003
From: pep308vote@hotmail.com (Raymond Hettinger)
Date: 10 Mar 2003 12:11:50 -0800
Subject: Summary of PEP 308 Vote for a Ternary Operator
Message-ID: <mailman.1047337743.7587.clpa-moderators@python.org>

The PEP 308 vote is summarized at:
  http://tinyurl.com/763f

Here are some of the highlights:

* 518 votes were received.  Of these, 82 used a RejectAll
  ballot and 436 used the original ballot.

* 363 had a preferred syntax they found acceptable while
  155 found no acceptable syntax.

* For the second ranked syntax, the ratio dropped to
  286:231 in favor of a change.  This means that 77 
  people found only one syntax to be acceptable.

* For the third ranked syntax, the ratio dropped to
  202:312.  This indicates that over half of the voters
  would prefer no change if they can't have one of 
  their first two choices.

* The highest ranked constructs were:

  235 for        (if C: x else: y)
  206 for        C ? x : y 

* The 235 breaks down to 177 accepting and 58 rejecting.
  If the RejectAll votes are attributed entirely to that
  syntax, the ratio becomes 177 favoring to 140 opposing.

* The individual votes were highly expressive and are
  worth reviewing:  

  http://tinyurl.com/75z2
  http://tinyurl.com/75z3

* The write-in votes had more accepts than rejects but
  had no clustering of syntax preferences.

* The downfall of all voting systems is not in the data
  collection, rather it is in the way the rankings are
  combined.  I avoid this issue by not declaring a
  winner.  Instead, Guido is being given a straight
  tally and a copy of all of the individual votes.
  This works especially well because his vote outweighs
  all of the others.

* Though the results leans toward accepting the PEP as
  proposed, it is not decisive.  Some of the no-change
  votes included strong pleas.  This will certainly be
  a consideration.

* There were three or four ballots received after this
  summary was prepared but before it was posted.  I'll
  include them for Guido in a separate email.  Please
  stop sending in new votes.


From pep308vote@hotmail.com  Mon Mar 10 23:29:13 2003
From: pep308vote@hotmail.com (Raymond Hettinger)
Date: 10 Mar 2003 15:29:13 -0800
Subject: Summary of PEP 308 Vote for a Ternary Operator
Message-ID: <mailman.1047350942.5882.clpa-moderators@python.org>

The PEP 308 vote is summarized at:
  http://tinyurl.com/763f

Here are some of the highlights:

* 518 votes were received.  Of these, 82 used a RejectAll
  ballot and 436 used the original ballot.

* 363 had a preferred syntax they found acceptable while
  155 found no acceptable syntax.

* For the second ranked syntax, the ratio dropped to
  286:231 in favor of a change.  This means that 77 
  people found only one syntax to be acceptable.

* For the third ranked syntax, the ratio dropped to
  202:312.  This indicates that over half of the voters
  would prefer no change if they can't have one of 
  their first two choices.

* The highest ranked constructs were:

  235 for        (if C: x else: y)
  206 for        C ? x : y 

* The 235 breaks down to 177 accepting and 58 rejecting.
  If the RejectAll votes are attributed entirely to that
  syntax, the ratio becomes 177 favoring to 140 opposing.

* The individual votes were highly expressive and are
  worth reviewing:  

  http://tinyurl.com/75z2
  http://tinyurl.com/75z3

* The write-in votes had more accepts than rejects but
  had no clustering of syntax preferences.

* The downfall of all voting systems is not in the data
  collection, rather it is in the way the rankings are
  combined.  I avoid this issue by not declaring a
  winner.  Instead, Guido is being given a straight
  tally and a copy of all of the individual votes.
  This works especially well because his vote outweighs
  all of the others.

* Though the results lean towards accepting the PEP as
  proposed, it is not decisive.  Some of the no-change
  votes included strong pleas.  This will certainly be
  a consideration.

* There were three or four ballots received after this
  summary was prepared but before it was posted.  I'll
  include them for Guido in a separate email.  Please
  stop sending in new votes.



Raymond Hettinger


From anthony@computronix.com  Mon Mar 10 23:31:48 2003
From: anthony@computronix.com (Anthony Tuininga)
Date: 10 Mar 2003 16:31:48 -0700
Subject: cx_Oracle 3.0
Message-ID: <mailman.1047350942.5883.clpa-moderators@python.org>

What is cx_Oracle?

cx_Oracle is a Python extension module that allows access to Oracle and
conforms to the Python database API 2.0 specifications with a few
exceptions.


Where do I get it?

http://computronix.com/utilities


What's new?

 1) Removed support for connection to Oracle7 databases; it is entirely
    possible that it will still work but I no longer have any way of 
    testing and Oracle has dropped any meaningful support for Oracle7
    anyway
 2) Fetching of strings is now done with predefined memory areas rather
    than dynamic memory areas; dynamic fetching of strings was causing
    problems with Oracle 9i in some instances and databases using a
    different character set other than US ASCII
 3) Fixed bug where segfault would occur if the '/' character preceded
    the '@' character in a connect string
 4) Added two new cursor methods var() and arrayvar() in order to
    eliminate the need for setinputsizes() when defining PL/SQL arrays
    and as a generic method of acquiring bind variables directly when
    needed
 5) Fixed support for binding cursors and added support for fetching
    cursors (these are known as ref cursors in PL/SQL)
 6) Eliminated discrepancy between the array size used internally and
    the array size specified by the interface user; this was done
    earlier to avoid bus errors on 64-bit platforms but another way has
    been found to get around that issue and a number of people were
    getting confused because of the discrepancy
 7) Added support for the attribute "connection" on cursors, an optional
    DB API extension
 8) Added support for passing a dictionary as the second parameter for
    the cursor.execute() method in order to comply with the DB API more
    closely; the method of passing parameters with keyword arguments is
    still supported and is in fact preferred
 9) Added support for the attribute "statement" on cursors which is a
    reference to the last SQL statement prepared or executed
10) Added support for passing any sequence to callproc() rather than
    just lists as before
11) Fixed bug where segfault would occur if the array size was changed
    after the cursor was executed but before it was fetched
12) Ignore array size when performing executemany() and use the length
    of the list of arguments instead
13) Rollback when connection is closed or destroyed to follow DB API
    rather than use the Oracle default (which is commit)
14) Added check for array size too large causing an integer overflow
15) Added support for iterators for Python 2.2 and above
16) Added test suite based on PyUnitTest
17) Added documentation in HTML format similar to the documentation for
    the core Python library

-- 
Anthony Tuininga
anthony@computronix.com
 
Computronix
Distinctive Software. Real People.
Suite 200, 10216 - 124 Street NW
Edmonton, AB, Canada  T5N 4A3
Phone:	(780) 454-3700
Fax:	(780) 454-3838
http://www.computronix.com



From guido@python.org  Tue Mar 11 20:42:16 2003
From: guido@python.org (Guido van Rossum)
Date: Tue, 11 Mar 2003 15:42:16 -0500
Subject: PSF obtains favorable advance ruling from IRS
Message-ID: <mailman.1047416403.4239.clpa-moderators@python.org>

I'm very pleased to announce that the Python Software Foundation has
been recognized by the IRS (the US office of taxation) as a tax-exempt
non-profit foundation (aka 501(c)(3)), and that the IRS has given the
PSF a "favorable advance ruling" on the PSF's application for
recognition as a public charity.  Read the IRS ruling here:

    http://www.python.org/psf/records/tax-exempt.txt

Recognition as a public charity has many benefits for the PSF and our
community, including strong requirements for public disclosure and
accountability, strong legal protections, and freedom from Federal
taxation on foundation revenue.  Contributions to the PSF are also
tax-deductible for purposes of US income tax, subject to the same
regulations as donations to any public charity.

The PSF hasn't solicited contributions so far, waiting for the IRS
ruling.  Now that we have a favorable advance ruling, as the letter
states we need to demonstrate broad public financial support to retain
public charity status.  A PSF committee is looking into ways to make
contributing as easy as possible (like "click here to donate").  If
you can't wait, the best way to contribute now is via check:

    http://www.python.org/psf/donations.html

The PSF currently has financial responsibility for PyCon DC 2003:

   http://www.python.org/pycon/

Provided that doesn't bankrupt us :-), other things the PSF does (and
would like to do) are given in the PSF's mission statement:

    http://www.python.org/psf/mission.html

So get those donations coming!

(Non-US residents are encouraged to donate, and their donations will
be counted as public financial support, but such donations are
generally not tax-exempt for the donor.  To change this would require
setting up PSF subsidiaries in many countries; we don't have the
resources to do this.  Check your local tax law; there may be
exceptions.)

--Guido van Rossum (home page: http://www.python.org/~guido/)


From tundra@tundraware.com  Tue Mar 11 20:30:08 2003
From: tundra@tundraware.com (Tim Daneliuk)
Date: 11 Mar 2003 20:30:08 GMT
Subject: [ANN]: twander 3.134 Released And Available
Message-ID: <mailman.1047416403.4240.clpa-moderators@python.org>

'twander' Version 3.134 is now released and available for download at:

          http://www.tundraware.com/Software/twander

The last public release was 3.0.

Existing users should upgrade immediately as this release contains
substantial bug fixes and many new features.

This release also introduces these new features:

   1) Ability to sort by any column

   2) Ability to use regular expressions to select directories or files

   3) Ability to maintain a single configuration file for all systems and
      users by means of new conditional statements and include directive
      in the configuration language.

Complete details of all fixes, changes, and new features can be found in
the WHATSNEW.txt file included in the distribution.

Users are strongly encourage to join the twander-users mailing list as
described in the documentation.


What Is 'twander'?
------------------

'twander' is a macro-programmable Filesystem Browser which runs on both
Unix-like systems as well as Win32 systems. It embraces the best ideas
of both similar GUI-driven programs (Konqueror, Windows Explorer) as
well as text-based interfaces (Midnight Commander, List, Sweep).


Or, If You Prefer The "Elevator Pitch"
--------------------------------------

'twander' is:

    - A better file browser for Unix and Win32. (Tested on FreeBSD, Linux, Win32.)
    - A way to make browsing the same on all the OSs you use.
    - A macro-programmable tool that lets *you* define the features.
    - A GUI navigation front-end for your shell.
    - A way to "can" workflows for your technically-challenged colleagues.
    - A way to free yourself from the shackles of the mouse.
    - A way to significantly speed up your day-to-day workflow.
    - A Python/Tkinter application - about 3100/1300 lines of code/comments
    - A RCT (Really Cool Tool) that will have you addicted in a day or two

See the web page for more information and a screen shot. Better still,
download the tarball and read the documentation.


------------------------------------------------------------------------------
Tim Daneliuk
tundra@tundraware.com





From brett@python.org  Wed Mar 12 21:36:59 2003
From: brett@python.org (Brett Cannon)
Date: Wed, 12 Mar 2003 13:36:59 -0800 (PST)
Subject: Care to sprint on the core at PyCon?
Message-ID: <mailman.1047506103.25252.clpa-moderators@python.org>

Four members of PythonLabs will be at the pre-PyCon sprint (more info on
sprints at http://www.python.org/cgi-bin/moinmoin/SprintPlan ) running one
for the Python core.  If you would like to attend, email me at
brett@python.org to say so.  You must be registered for PyCon to be able
to attend.  And please do this ASAP so we can get the ball rolling on this
and lock down who will be there.

And regardless whether you care to attend or not, please look at
http://www.python.org/cgi-bin/moinmoin/PyCoreSprint and make suggestions
on what the group should sprint on.

-Brett


From wesc@fuzzyorange.com  Tue Mar 11 22:23:27 2003
From: wesc@fuzzyorange.com (Wesley Chun)
Date: Tue, 11 Mar 2003 14:23:27 -0800 (PST)
Subject: ANN: BayPIGgies mtg Wed Mar 12 7:30pm
In-Reply-To: <Pine.LNX.4.31.0302111621570.10147-100000@emperor.deirdre.org>
Message-ID: <mailman.1047506342.30479.clpa-moderators@python.org>

BayPIGgies: Silicon Valley-San Francisco Bay Area Python Users Group

When:     March 12, 2002 @ 7:30pm
Where:    Stanford University, Palo Alto, CA
Agenda:   PyChecker and Friends
Speaker:  Phil Lindsay

"PyChecker and friends: Easing the transition from ad hoc scripts to
stable, maintainable Python applications"

PyChecker can be thought of as "Lint" for Python, and is a tool for
finding bugs in Python source code. This talk will introduce PyChecker,
show some of its functionality and discuss some of the lessons learned
from its use in a commercial software development environment. The
presentation will be from the perspective of a happy user & interested
hacker. Some of the future goals of the project's authors will also be
described. If time permits, the speaker will demonstrate a couple of
small tools he has developed to also help in the creation of stable,
maintainable applications.

# Call For Talks: We are actively seeking speakers for BayPIGgies! If you
would like to give a talk at one of our 2003 meetings (any Python related
topic), contact us to coordinate!

more info including directions:    http://www.baypiggies.net

hope 2 c u tomorrow nite!

-wesley

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

"Core Python Programming", Prentice Hall PTR, =A9 2001
    http://starship.python.net/crew/wesc/cpp/

Silicon Valley-San Francisco Bay Area Python Users Group (BayPIGgies)
    http://baypiggies.net

wesley.j.chun :: wesc at deirdre.org or wesc at fuzzyorange.com
cyberweb.consulting : henderson, nv : cyberweb at rocketmail.com
http://www.roadkill.com/~wesc/cyberweb/



From erellon@narod.ru  Wed Mar 12 04:44:43 2003
From: erellon@narod.ru (erellon)
Date: 11 Mar 2003 20:44:43 -0800
Subject: Python ANT  (PyANT) version 0.31 released
Message-ID: <mailman.1047506342.30480.clpa-moderators@python.org>

PyANT is a project for porting Jakarta's ANT ideas to Python.
The main advantage it has over Java is speed and support for 
Python scripts. PyANT written in pure Python and project intended for
developers
who wants to automate their projects building and testing process.
Project link here: 
  http://www.sourceforge.net/projects/pyant

Changes since last version:
	- Fixed bug in copying single file to single file
	+ Added attribute "dir" for <fileset> for compatibility with ANT.
	  "basedir" attribute still works
	+ Added conditional attributes to <target>
	  for now constructions <target if="propertyname">
	  and <target unless="propertyname">
	  sample included in "samples/build_iftest.xml"
	+ Added <Config> task to read and write Python config files (.INI like)
	+ Added <Tar> task to create .tar and .tar.gz archives
	+ Added <Input> and <Dirname> tasks that are compilant with ANT tasks
	  with same names
	+ Added "regkey" handler, this handler allows to access registry keys
	  on Win32 platform via full path to that key.
	  Sample usage provided in "build_handlers.xml" example file
	+ Added <Checksum> task, that is like in ANT spec and supports 
	  MD5 and SHA algorithms

Note:
  Project files available as ZIP, TGZ and EXE-self installer with Inno
Setup files


Ivan Begtin aka Erellon (erellon%narod.ru)


From robin@alldunn.com  Wed Mar 12 06:30:43 2003
From: robin@alldunn.com (Robin Dunn)
Date: Tue, 11 Mar 2003 22:30:43 -0800
Subject: ANNOUNCE:   wxPython 2.4.0.5
Message-ID: <mailman.1047506343.30482.clpa-moderators@python.org>

Close on the heels of 2.4.04, wxPython 2.4.0.5 is now available for 
download at http://wxpython.org/download.php

wxPython is a popular cross platform GUI toolkit for the Python language 
that supports running Python apps on Win32, Mac OSX, and Linux/Unix 
systems, using native widgets and therefore natiove look and feel on the 
respective plafroms.

 From the webpage given above you can download source code, 
documentation and pre-built wxPython packages for various platforms and 
for various versions of Python (2.1, 2.2 or 2.3, except for OS X which 
only has a build for 2.3)

The 2.4.0.5 release solves several small but annoying bugs, and includes 
updates of the colourchooser and PyCrust pacakges.

For details of the 2.4.0.4 or earlier releases please look here: 
http://wxpython.org/CHANGES.txt

-- 
Robin Dunn
Software Craftsman
http://wxPython.org  Java give you jitters?  Relax with wxPython!




From aahz@pythoncraft.com  Thu Mar 13 04:37:58 2003
From: aahz@pythoncraft.com (Aahz)
Date: Wed, 12 Mar 2003 23:37:58 -0500
Subject: PyCon: two more days for checks
Message-ID: <mailman.1047558182.2181.clpa-moderators@python.org>

March 15 is the deadline if you want to get the $200 pre-conference
price by paying with check; the envelope containing your check must be
postmarked on or before March 15.  You have until March 21 if you pay by
credit card.

http://www.python.org/pycon/reg.html

PyCon DC 2003

   The first PyCon will be held 26-28 March, 2003, at George Washington
   University's Cafritz Conference Center in Washington DC. There will be
   a development sprint Mon/Tues before the conference.

   PyCon is a community-oriented conference targeting developers (both
   those using Python and those working on the Python project). It gives
   you opportunities to learn about significant advances in the Python
   development community, to participate in a programming sprint with
   some of the leading minds in the Open Source community, and to meet
   fellow developers from around the world. The organizers have worked
   hard to ensure that the conference be affordable and accessible to
   all. We look forward to seeing you there.
-- 
Aahz (aahz@pythoncraft.com)           <*>         http://www.pythoncraft.com/

Register for PyCon now!  http://www.python.org/pycon/reg.html



From mal@lemburg.com  Thu Mar 13 12:06:30 2003
From: mal@lemburg.com (M.-A. Lemburg)
Date: Thu, 13 Mar 2003 13:06:30 +0100
Subject: Local Python Meeting in Duesseldorf, Germany
In-Reply-To: <3E6708BA.4000601@lemburg.com>
References: <3E625AE8.6070806@lemburg.com>	<200303050841.34188.bplatzen@sosnetz.de> <3E65F9B1.8070509@lemburg.com>	<200303052156.04062.bplatzen@sosnetz.de> <3E6708BA.4000601@lemburg.com>
Message-ID: <mailman.1047558183.2192.clpa-moderators@python.org>

This is an annoucement for a local Python meeting in Germany,
so please excuse that the rest of this message is in German.

---------------------------------------------------------------------

* D=FCsseldorfer Python Treffen

Einige Python-Enthusiasten wollen sich am 17.03. um 20 Uhr
ganz ungezwungen im Tigges treffen. Vortr=E4ge u.=E4. sind nicht
geplant. Alle Python-Freunde/innen sind herzlich eingeladen.
Vielleicht gibt es ja doch mehr davon in der Region um
D=FCsseldorf, als wir bisher annahmen :-)

* Wie kommt man zum Tigges ?

Hier ist ein elektronischer Fahrplan:

      http://efa.vrr.de/

Die Haltestelle hei=DFt "Bilk-S".

Das Tigges liegt in unmittelbarer N=E4he des S-Bahnhofs Bilk:
Brunnenstra=DFe Nr.1.

Hier einige weitere Infos:

      http://www.linux.de/groups/show.php3?place=3DD%FCsseldorf

Das sollte reichen, um das Tigges zu finden :-)

Bis dann,
--=20
Marc-Andre Lemburg
eGenix.com

Professional Python Software directly from the Source  (#1, Mar 13 2003)
>>> Python/Zope Products & Consulting ...         http://www.egenix.com/
>>> mxODBC, mxDateTime, mxTextTools ...        http://python.egenix.com/
________________________________________________________________________
Python UK 2003, Oxford:                                     19 days left
EuroPython 2003, Charleroi, Belgium:                       103 days left



From uche.ogbuji@fourthought.com  Thu Mar 13 15:23:25 2003
From: uche.ogbuji@fourthought.com (Uche Ogbuji)
Date: Thu, 13 Mar 2003 08:23:25 -0700
Subject: Article: Using SAX for Proper XML Output
Message-ID: <mailman.1047570727.1379.clpa-moderators@python.org>

http://www.xml.com/pub/a/2003/03/12/py-xml.html

I demonstrate how to use the SAX |xml.sax.XMLGenerator, available in 
core Python, |to generate XML.

-- 
Uche Ogbuji                                    Fourthought, Inc.
http://uche.ogbuji.net    http://4Suite.org    http://fourthought.com
Universal Business Language (UBL) - http://www-106.ibm.com/developerworks/xml/library/x-think16.html
EXSLT by example - http://www-106.ibm.com/developerworks/library/x-exslt.html
The worry about program wizards - http://www.adtmag.com/article.asp?id=7238
Use rdf:about and rdf:ID effectively in RDF/XML - http://www-106.ibm.com/developerworks/xml/library/x-tiprdfai.html
Keep context straight in XSLT - http://www-106.ibm.com/developerworks/xml/library/x-tipcurrent.html
Python Generators + DOM - http://www.xml.com/pub/a/2003/01/08/py-xml.html
Simple XML Processing With elementtree - http://www.xml.com/pub/a/2003/02/12/py-xml.html




From uwe.schmitt@procoders.net  Thu Mar 13 12:38:06 2003
From: uwe.schmitt@procoders.net (Uwe Schmitt)
Date: 13 Mar 2003 12:38:06 GMT
Subject: SandBox.py new version
Message-ID: <mailman.1047570726.1355.clpa-moderators@python.org>

[ This is a repost of the following article:                               ]
[ From: Uwe Schmitt <uwe.schmitt@procoders.net>                            ]
[ Subject: SandBox.py new version                                          ]
[ Newsgroups: comp.lang.python                                             ]
[ Message-ID: <b4pkcb$eao0$1@hades.rz.uni-saarland.de>                     ]

Hi,

I updated SandBox.py to version 0.5.  SandBox.py allows
executing python code in a restricted environment.

New Features:
standard configuration for easy use, file object proxies which
restrict file objects to given directories and access modes,
importing of classes, test code which explains full functionality
of SandBox.py and some more.

Download/More Info:
http://pythonstuff.procoders.net

This module might be interesting for the users of the withdrawn
modules rexec/bastion because thy where cracked. 
I found the hacks on the python dev mailing list and they do not 
work for SandBox.py.

I really appreciate any comments on bugs and vulnerabilities.
Just drop a note to our board at http://board.procoders.net.

Greetings, Uwe.

-- 
Dr. rer. nat. Uwe Schmitt      Computer science is no more about Computers,
uwe.schmitt@num.uni-sb.de      than astronomy is about telescopes. (Dijkstra)
http://www.procoders.net           

-- 
Dr. rer. nat. Uwe Schmitt      Computer science is no more about Computers,
uwe.schmitt@num.uni-sb.de      than astronomy is about telescopes. (Dijkstra)
http://www.procoders.net           


From ianb@colorstudy.com  Thu Mar 13 21:14:50 2003
From: ianb@colorstudy.com (Ian Bicking)
Date: 13 Mar 2003 15:14:50 -0600
Subject: ANN: SQLObject 0.2.1
Message-ID: <mailman.1047600541.12499.clpa-moderators@python.org>

SQLObject 0.2.1 has been released, fixing a caching bug, adding SQLite
support, and optimizing selects.

SQLObject is now a SourceForge project, with its own web page, mailing
list, and CVS repository.  Details at:

    http://sqlobject.org

What is SQLObject?
------------------

SQLObject is an object-relational mapper. It allows you to translate
RDBMS table rows into Python objects, and manipulate those objects to
transparently manipulate the database.



-- 
Ian Bicking  ianb@colorstudy.com  http://colorstudy.com
4869 N. Talman Ave., Chicago, IL 60625  /  773-275-7241
"There is no flag large enough to cover the shame of 
 killing innocent people" -- Howard Zinn



From uwe.schmitt@procoders.net  Thu Mar 13 21:06:24 2003
From: uwe.schmitt@procoders.net (Uwe Schmitt)
Date: 13 Mar 2003 21:06:24 GMT
Subject: SandBox.py new version
References: <mailman.1047570726.1355.clpa-moderators@python.org>
Message-ID: <mailman.1047600542.12500.clpa-moderators@python.org>

Uwe Schmitt <uwe.schmitt@procoders.net> wrote:
> Hi,

> I updated SandBox.py to version 0.5.  SandBox.py allows
> executing python code in a restricted environment.

Sorry but Jason Harper discovered some bugs in the new
code, there is no problem with the overall design but
I'll have to spend some hours on code fixing.
The interface will not change so you can try Sandbox
but do *not* use it in a productive environment.
It is stil v0.5.

Greetings, Uwe


-- 
Dr. rer. nat. Uwe Schmitt      Computer science is no more about Computers,
uwe.schmitt@num.uni-sb.de      than astronomy is about telescopes. (Dijkstra)
http://www.procoders.net           


From uwe.schmitt@procoders.net  Thu Mar 13 22:29:22 2003
From: uwe.schmitt@procoders.net (Uwe Schmitt)
Date: 13 Mar 2003 22:29:22 GMT
Subject: SandBox.py new version
References: <mailman.1047570726.1355.clpa-moderators@python.org>
Message-ID: <mailman.1047600543.12501.clpa-moderators@python.org>

Uwe Schmitt <uwe.schmitt@procoders.net> wrote:


I just updated the sandbox module, there were some minor
bugs and wrong identations.

There is still a problem concerning bad memory management
which I will fix as soon as possible.

Be aware that the code is still v0.5 and should not be
used in sensitive applications.

Greetings, Uwe


-- 
Dr. rer. nat. Uwe Schmitt      Computer science is no more about Computers,
uwe.schmitt@num.uni-sb.de      than astronomy is about telescopes. (Dijkstra)
http://www.procoders.net           


From ugny-0303@unigroup.org  Fri Mar 14 04:29:14 2003
From: ugny-0303@unigroup.org (Unigroup of New York)
Date: Thu, 13 Mar 2003 23:29:14 -0500 (EST)
Subject: LOCAL NYC UNIGROUP 20-MAR-2003 MEETING: Python and Twisted
Message-ID: <mailman.1047644522.3146.clpa-moderators@python.org>

Content-Type: multipart/mixed;
 boundary="------------892EFEC503A67B315CFF5743"
Lines: 382
Date: Fri, 14 Mar 2003 04:29:12 GMT
NNTP-Posting-Host: 24.46.112.146
X-Trace: news4.srv.hcvlny.cv.net 1047616152 24.46.112.146 (Thu, 13 Mar 2003 23:29:12 EST)
NNTP-Posting-Date: Thu, 13 Mar 2003 23:29:12 EST

This is a multi-part message in MIME format.
--------------892EFEC503A67B315CFF5743
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

 
--------------892EFEC503A67B315CFF5743
Content-Type: text/plain; charset=us-ascii;
 name="0"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="0"


Subject: LOCAL NYC UNIGROUP 20-MAR-2003 MEETING: Python and Twisted


=============================================
UNIGROUP OF NEW YORK MARCH 2003 ANNOUNCEMENTS
=============================================

   --------------------------------------------------
1. UNIGROUP'S MARCH 2003 GENERAL MEETING ANNOUNCEMENT
   --------------------------------------------------

      When:  Thursday, March 20th, 2003

     Where:  The Chase Manhattan Bank
             One Chase Manhattan Plaza (1CMP)  <==(Our New Location!)
             Conference Center, 28th Floor
             Downtown, NYC
             **********************************************
             YOU MUST RSVP TO GET PAST SECURITY, SEE BELOW!
             **********************************************

      Time:  6:15 PM - 6:30 PM  Registration
             6:30 PM - 6:40 PM  Ask the Wizard,
                                Questions, Answers and Current Events
             6:40 PM - 6:50 PM  Unigroup Business
             6:50 PM - 9:30 PM  Main Presentation

             ------------------
     Topic:  Python and Twisted
             ------------------

   Speaker:  Itamar Shtull-Trauring,        <http://itamarst.org>
             Chief Technical Architect,
             Zoteca, Inc.                   <http://www.zoteca.com>


   Introduction:
   -------------

   If you take a look at Python.org, you'll learn that a Python is
   "an enormous non-poisonous serpent"...  which speaks a "totally
   awesome language that will someday crush the $'s out of certain
   other so-called VHLL's".  Python (the software) is a freely
   usable and freely distributable, interpreted, interactive,
   object-oriented programming language, which is often compared
   to TCL, Perl, Scheme and Java.

   Unigroup has addressed Java and Perl topics at previous meetings,
   and now the time has finally arrived to present Python!

   -------------------------------------------------------------------

   SPECIAL INSTRUCTIONS:
   ---------------------

   * IN ORDER TO PASS THROUGH SECURITY AT CHASE, WE NEED YOU TO RSVP
   * PRIOR TO THE MEETING DAY, SO WE CAN GET YOUR NAME ON THE ATTENDEE
   * LIST.  ADVANCE REGISTRATION AND PHOTO ID ARE REQUIRED!
   * RSVP DEADLINE 19-MAR-2003 16:00.  <<<< PAY ATTENTION, DEADLINE!
   * Keep an eye out on the deadline date and time, as it may change.

   Please RSVP if you know you are attending or if you think you may
   be attending.  This will help us arrange for a letter to security
   for all of Unigroup.  It will also help us to determine the correct
   amount of food and refreshments.

   To REGISTER for this event, please RSVP by:

   a) If at all possible, please use the Unigroup Registration Page:
         http://www.unigroup.org/unigroup-rsvp.html
      This will allow us to have some automation in the RSVP process.

   b) If you must Email us, send an EMail containing the FIRST and
      LAST NAMEs of the persons attending to the Unigroup RSVP
      address:
         unigroup-rsvp@unigroup.org
      The Email subject should start with "RSVP".
      You may optionally include your contact phone number (that
      day) or other current information.

      DO NOT simply reply to this announcement, sending us back the entire
      announcement (we already have it); leaving the subject as it
      was, and NOT containing the phrase "RSVP" as requested.  In
      that case, your message just looks like failed mail and it
      makes it impossible to automate the RSVP process and get
      you registered for our event.

      ALSO: Do NOT give us an Email address which is over quota
      and cannot receive any new Email.  This causes us to receive
      bounces from your address when we send out the RSVP-ACKs.
      You must have a working and valid Email address in order
      to get on the Unigroup Meeting Attendee List which will
      grant you access to our meetings.  Be sure to proof-read
      your Email address before submitting the RSVP request.

   Please continue to check the Unigroup web site:
        http://www.unigroup.org
   for any last minute updates concerning this meeting.  Please
   check your Email for any last minute announcements prior to the
   meeting.  Note that only the Attendee First and Last Names will
   be provided to Chase Security.

   -------------------------------------------------------------------

   Description of Talk:
   --------------------

   This talk will be a quick overview of the Python programming
   language, it's uses, and the motivation for using it.  Twisted
   will then be presented, as an example of the power and flexibility
   of Python, and as a useful framework for a wide range of network
   programs.

   The Python-in-Business site tells us this about Python:
   ``Python is a very high level programming language that excels in
   clarity and simplicity of expression.  Python allows programmers
   to build their computing solutions using human modes of thought
   and logic.  While Python is relatively simple to learn and use,
   its extensive standard library, portability, and ability to
   integrate tightly with other languages make it a real power tool
   for many types of software development.''  Python is used by many
   organizations and companies, including Google, Industrial
   Light & Magic, Redhat, Lawrence Livermore National Laboratories
   and others.   For information see <http://www.python.org> and
   <http://www.python-in-business.org/>.

   The Twisted event-driven networking framework is a powerful,
   cross-platform tookit for creating networked applications.  It
   is being used to create server applications, GUI clients and
   peer-to-peer systems, both open source and in large
   organizations such as NASA.  Twisted's support for multiple
   protocols (TCP, UDP, SSL/TLS, Multicast, Sockets, HTTP, SSH,
   FTP, etc), multiple platforms (Unix, Win32) and integrated
   services make it a great choice for the next generation of
   networked applications.  Twisted is written in Python, and is
   licenced under the LGPL.  For more information see
   <http://www.twistedmatrix.com>.


   Web Resources:
   --------------

   Python              http://www.python.org
   Python Newsgroup    news://comp.lang.python
   Python-in-Business  http://www.python-in-business.org
   Twisted             http://www.twistedmatrix.com


   Giveaways:
   ----------

   O'Reilly has been kind enough to provide us with some of their
   books, which we will raffle off as giveaways at our meetings.


   Speaker Biography:
   ------------------

   Itamar Shtull-Trauring has been programming since 1994.  He has
   worked on projects ranging from multimedia applications, to web
   sites, distributed servers and remote object protocols.  He has
   contributed to Python, Zope and is one of the main developers
   of Twisted.  Currently he is Chief Technical Architect at
   Zoteca.  For a full resume see <http://itamarst.org/resume.html>.


   Company Biography:
   ------------------

   Zoteca <http://www.zoteca.com> provides open source / open
   standards software solutions and consulting services.  Their
   technology solutions and expertise address a broad range of
   IT challenges including Enterprise Application Integration,
   complex web site back-ends and distributed network applications.
   Zoteca's key technology platform is a software workbench for the
   rapid development of efficient, safe, robust and scalable
   applications used in distributed, networked environments.


   -------------------------------------------------------------------

   Fee Schedule:
         Yearly Membership (includes all meetings):      $ 50.00
       * Non-Member Single Meeting:                      $ 20.00
         Student Yearly Membership:                      $ 20.00
         Non-Member Student Single Meeting (with ID):    $  5.00
         Payment Methods: Cash, Check, American Express.

       * Employees of JPM/Chase (with ID) can attend general
         meetings at NO CHARGE.

    ==>  Unigroup is the Greater NYC Regional Area Affiliate
         of UniForum - an International Unix Users Group.
         Our Joint Membership Program with UniForum is currently
         on hold due to circumstances at UniForum.  For information
         about UniForum visit http://www.uniforum.org.

   -------------------------------------------------------------------

   Complimentary Food and Refreshments will be served.  This includes
   sandwiches such as turkey, roast beef, chicken, tuna and grilled
   eggplant.  Chase also provides us a very nice spread of treats,
   which include brownies, cookies, popcorn, bottled water and
   assorted beverages.

   -------------------------------------------------------------------

   Directions:

     The 1CMP building is situated: South of Liberty Street, North
     of Pine Street, East of Broad/Nassau Street and West of William
     Street.  The building is one block east of Broadway, right
     behind 140 Broadway.

     The closest entrance to the conference center is from Nassau
     Street, first elevator bank from the Nassau Street entrance.

     The building is on a raised platform.  Walk up the outside
     stairs at Nassau Street and head for the guard's station at the
     south-west corner of the building.  Tell the guards you are
     heading for Unigroup.

     They will inspect your ID and carry-ins and direct you to the
     meeting facility assuming you are on the Unigroup RSVP list.

     Once you get upstairs, enter the conference facility through
     its main doors.  There is a bank of large monitors to the left
     of the entrance which should direct you to the Unigroup meeting
     room (the room may vary from month to month).  To the right of
     the main entrance is the concierge's desk, ask for help there
     if you need anything.  The conference facility has two levels,
     keep in mind that the Unigroup meeting may be up the staircase
     on its upper level.  Thus far, our meeting room has been
     upstairs, on the south side of the building.

     As always, also look out for Unigroup signs marking the path
     to the meeting room.  Also note, if you come early, we may not
     have our own signs in place yet (we have to commute there too).

     Transit By Train:  Take the J/M/Z to Broad Street and walk one
     block North to Pine St.  Take the 4/5 to Wall Street and walk
     North to Pine St., then East to Broad St.  Take the 2/3 to Wall
     Street, the North West exit is inside the Chase complex, else
     you will need to walk a block North and West.  See the MTA
     Downtown NYC Map (pdf) for detailed mass transit information:
       http://www.mta.nyc.ny.us/nyct/maps/mapdown.pdf

   -----

   Please mark this meeting on your calendar and join us!
   Please tell your friends about Unigroup!

------------------------------------------------------------------------------
------------------------------------------------------------------------------

   -----------------
2. UPCOMING MEETINGS
   -----------------

   We have a series of meetings in the works:

   - Python and Twisted
   - True64/HPUX/Linux Futures (watch for a Field Trip meeting)
   - Zope (Web Page Development)
   - Unix Clusters and Clustered Databases
   - High Performance Internet Servers / Web Acceleration
   - Unix 30th Birthday Celebration
   - IPsec and IPv6
   - Linux Clustering Part 3: Beowulf version 2
   - Building a Firewall using FreeBSD and Linux
   - Unix Office Tools: Word Processors, Spreadsheets, Accounting Packages.
   - Emacs
   - Tex
   - PKI
   - GNU Development Environments
   - Meetings on a variety of Sun/Solaris/Java topics

   Please let us know about any other meeting topics that you may be
   interested in.  Potential speakers on Unix related technology topics
   should contact the Unigroup board at ugny-0303@unigroup.org.

------------------------------------------------------------------------------
------------------------------------------------------------------------------

   -------------
3. PRIOR MEETING
   -------------

   Unigroup would like to thank our speaker Sharon M. Williams, from
   HP BCRS, for her presentation "IT Disaster Recovery - Running a
   Winning Relay Race".  Ms. Williams focused on the business aspects
   of the Recovery Time Objective (RTO) and Recovery Point Objective (RPO)
   and the processes of Respond/Recover/Restore/Resume.  Ownership (by
   departments, by people) of the various tasks along the way was critical
   to an orderly recovery.  The logistics of recovery "relay teams" and
   backup/recovery sites was also discussed.  Detailed planning and dress
   rehearsals are required such that everyone involved in the recovery knows
   the task they need to perform.  Key management personnel must know their
   roles in order to have proper decision making, and funding must also be
   available for use during the recovery process (car rental, air-fare,
   train-fare, hotel, computers, hubs, food, etc).  We also heard some
   interesting war stories concerning what can go wrong and just how
   probable the unexpected can be.

------------------------------------------------------------------------------
------------------------------------------------------------------------------

   --------------------
4. UNIGROUP INFORMATION
   --------------------

   Unigroup is one of the oldest and largest Unix User's Groups serving
   the Greater New York City Regional Area since the early 1980s.  Unigroup
   is a not-for-profit, vendor-neutral and member funded volunteer
   organization.  Unigroup holds regular and special event meetings
   throughout the year on technical topics relating to Unix and the Unix
   User Community.  Unigroup is also the Greater NYC Regional Area Affiliate
   of UniForum - an International Unix Users Group.

   Thanks to Chase, Unigroup holds regular meetings planned for the Third
   THURSDAY of Odd Months at The Chase Manhattan Bank, 1CMP, NYC.
   Chase has been a long time sponsor of Unigroup, allowing us the use of
   a meeting room and presentation equipment.

   Planned meeting dates are: 3/20/2003, 5/15/2003, 7/17/2003, 9/18/2003...
   Watch for our Special Event meetings at the various trade shows in NYC
   as well as "field trips" to the facilities of local hardware and
   software vendors.

   =========================================================================
   = For Unigroup Information, Events and Meeting Announcements be sure to =
   = visit our World Wide Web Home Page:                                   =
   =       http://www.unigroup.org                                         =
   =========================================================================

   For further information or to get on the Unigroup Electronic Mail Mailing
   List send an EMail message to:
        ugny-0303@unigroup.org

   To contact the Board of Directors of Unigroup, send an EMail message to:
        ugny-0303@unigroup.org

   To contact the Newsletter Editor, send an EMail message to:
        ugny-0303@unigroup.org

   If you have recently attended a meeting and you are not receiving
   Email announcements, please send us an Email and we will make
   corrections to our lists.

   Please Email the Board with any suggestions, especially potential
   meeting topics and speakers.  Unigroup welcomes contributions and
   content suggestions for our newsletter.  Unigroup is a volunteer
   organization and we need your assistance!  Please let us know if you
   can help!

------------------------------------------------------------------------------
------------------------------------------------------------------------------

I hope to see you all at our next meeting!

-Rob Weiner
 Unigroup Executive Director
 ugny-0303@unigroup.org
 http://www.unigroup.org


--------------892EFEC503A67B315CFF5743--


From jiba@tuxfamily.org  Fri Mar 14 12:32:56 2003
From: jiba@tuxfamily.org (Jiba)
Date: Fri, 14 Mar 2003 13:32:56 +0100
Subject: Soya3D 0.3.1 and PyOpenAL 0.1
Message-ID: <mailman.1047852482.12604.clpa-moderators@python.org>

I want to announce Soya3D 0.3.1 (bugfix release) and PyOpenAL 0.1.

*** What is Soya3D ???

Soya3D is a high level 3D engine for Python, designed with game in mind.
It relies on OpenGL and SDL.
Soya is written partly in Python and partly in C; our goal is to provide a full architecture for making free (GPL) game of professionnal quality entirely in Python.

*** What is PyOpenAL ???

PyOpenAL is an OpenAL binding for Python. OpenAL is a 3D sound library.
PyOpenAL includes a module for integrating it with Soya.
It can read wave and Ogg Vorbis file (require PyOgg and PyVorbis).


Both are available under the GPL, and are known to work under Linux ; a port of Soya to windows is upcoming.

http://oomadness.tuxfamily.org/en/soya
http://oomadness.tuxfamily.org/en/pyopenal


BTW be sure to check the Slune game, a 3D game written in Python with Soya and PyOpenAL !

http://oomadness.tuxfamily.org/en/slune

Jiba


From dave@davidcook.org  Sat Mar 15 01:15:26 2003
From: dave@davidcook.org (David M. Cook)
Date: Sat, 15 Mar 2003 01:15:26 GMT
Subject: Local: SANDPYT - San Diego Pythonistas March 20 meeting
Message-ID: <mailman.1047852482.12629.clpa-moderators@python.org>

SANDPYT, the San Diego Pythonistas will be having our monthly meeting on 
March 20, 2003 (3rd Thursday of the month) at

San Diego County Office of Education, room 306 (building #3)
6401 Linda Vista Road
San Diego, CA

For a map see

http://www.kernel-panic.org/uploads/images/7/sdcoe.gif

To subscribe to our mailing list visit

http://www.sandpyt.org/mailman/listinfo/sandpyt

Dave Cook



From detlev@die-offenbachs.de  Sat Mar 15 13:11:21 2003
From: detlev@die-offenbachs.de (Detlev Offenbach)
Date: Sat, 15 Mar 2003 14:11:21 +0100
Subject: ANN: Eric 3.1 released
Message-ID: <mailman.1047852484.12658.clpa-moderators@python.org>

Hi,

After some time of heaving coding I am proud to announce that Eric 3.1 is
available for download via

http://www.die-offenbachs.de/detlev/eric3.html

This version includes a CVS interface, an interface to Happydoc, 
additional debug clients (standard, a Qt free and a variant for 
debugging multithreaded apps). It has a bunch of bugs fixed and is now 
very well tested on Windows platforms (thanks to Andrew Bushnell of 
Fluent Inc.). For details see the history file in the distribution.

What is it?
-----------
Eric 3.1 (or short eric3) is a Python IDE written using PyQt and 
QScintilla. It has integrated project management capabilities, it gives 
you an unlimited number of editors, an integrated Python shell, an 
integrated debugger and much more.

Please see for yourself by visiting the a.m. page (it contains a picture 
of Eric our mascot as well).

Please report bugs, feature wishes or code contributions to 
eric-bugs@die-offenbachs.de

Help wanted!!
-------------
I would need some support in the area of more translations and user 
documentation. Any volunteers out there? Just let me know.

Regards,
Detlev
-- 
Detlev Offenbach
detlev@die-offenbachs.de


From i.linkweiler@web.de  Sat Mar 15 17:10:58 2003
From: i.linkweiler@web.de (Ingo Linkweiler)
Date: Sat, 15 Mar 2003 18:10:58 +0100
Subject: ANN: Von Stiften und Maeusen
Message-ID: <mailman.1047852484.12674.clpa-moderators@python.org>

SuM - Von Stiften und Mäusen

DESCRIPTION:
------------
German only: About pens and mice,
a conversion of the well-known didactical learning software to Python.
Perhaps an english version will follow in future.

BESCHREIBUNG:
-------------
Eine Umsetzung der bekannten didaktischen Lernsoftware nach Python.

Einführung in die Grundlagen der objektorientierten Programmierung.
Anhand fertiger Klassen "Stift", "Maus", "Bildschirm" u.a. kann in
dieser Lernumgebung  der Einstieg in die objektorientierte 
Softwareentwicklung
mit einfacher Computergrafik vermittelt werden.

VERSION:
--------
1.0 erste öffentliche Version
1.1 zahlreiche Verbesserungen wurden vorgenommen.
Es erfolgten Anpassungen an die aktuelle Klassenbibliothek.
Zahlreiche Beispiele und eine komplett erneuerte Dokumentation 
demonstrieren die Anwendung.

URL:
----
http://www.ingo-linkweiler.de/diplom/



From logistix@zworg.com  Sun Mar 16 00:06:50 2003
From: logistix@zworg.com (logistix)
Date: 15 Mar 2003 16:06:50 -0800
Subject: PyXR 0.9- Cross-Referenced HTML from Python Source
Message-ID: <mailman.1047852486.12713.clpa-moderators@python.org>

PyXR 0.9- Cross-Referenced HTML from Python Source 

PyXR generates HTML pages from python source files.  It also attempts
to generate cross-referenced hyperlinks, which makes it
distinctive from the 8 million other prettyprinters out there.  It's
been tested on Python 2.2 and 2.3 for Windows, OpenBSD 3.2 and RedHat
7.3.  There's no reason it shouldn't work on other platforms with
minor configuration.

Major Improvements in version 0.9:
    Full integration with python's Library Reference Manual.  
        References to builtin functions, classes, etc link
        back to the Library Reference.  References to .pyds
        link back to the Library Reference.  All documented
        modules ultimately link back to the Library Reference.

    Option to continue on error when processing a file.  Version
        0.8 crashed if you had a .py file with invalid source
        in your pythonpath.

More information is available at:

    http://members.bellatlantic.net/~olsongt/python/pyxr.html

The package is available at:

    http://members.bellatlantic.net/~olsongt/python/PyXR.zip

Enjoy!


From dgrisby@apasphere.com  Sat Mar 15 19:27:13 2003
From: dgrisby@apasphere.com (Duncan Grisby)
Date: Sat, 15 Mar 2003 19:27:13 GMT
Subject: ANNOUNCE: omniORB 4.0.1 and omniORBpy 2.1
Message-ID: <mailman.1047852485.12694.clpa-moderators@python.org>

omniORB 4.0.1 and omniORBpy 2.1 are now available.

omniORB is a robust, high performance CORBA ORB for C++. omniORBpy is
a version for Python. They are freely available under the terms of the
GNU Lesser General Public License (for the libraries), and GNU General
Public License (for the tools). For more information, see

  http://omniorb.sourceforge.net/

These releases are minor updates from the previous stable releases.
Highlights of the new features are:

 - Per object reference and per-thread timeouts.
 - Complete interceptors.
 - Support for new platforms: MacOS, VxWorks, Digital Mars C++.
 - Small performance improvements.
 - Generation of Python stubs for all COS IDL.
 - New Python omniORB.any module to help convert to and from Anys.
 - Bug fixes.

The releases can be downloaded from

  http://sourceforge.net/project/showfiles.php?group_id=51138

Enjoy!

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan@grisby.org     --
   -- http://www.grisby.org --


From larry@thekompany.com  Mon Mar 17 01:38:33 2003
From: larry@thekompany.com (Larry Wright)
Date: Mon, 17 Mar 2003 01:38:33 GMT
Subject: PyQtDoc Now Available
Message-ID: <mailman.1047908642.18570.clpa-moderators@python.org>

PyQtDoc DOCUMENTATION TOOL FOR PYQT ON LINUX AND WINDOWS

Rancho Santa Margarita, CA -- 15 July 2000 -- theKompany.com, producers and
distributors of high-quality open source and commercial multi-platform
software, are pleased to announce the availability of PyQtDoc 1.0 
(http://www.thekompany.com/products/pyqtdoc/), a Windows/Linux 
application for providing rapid access to documentation for
the popular PyQt (http://www.riverbankcomputing.co.uk/) set of
Python bindings for Qt.

PyQtDoc fills the yawning chasm that exists for the popular PyQt project 
from Riverbank Computing. PyQt is also the basis for our popular 
BlackAdder product for Python development. PyQtDoc is included with your 
purchase of BlackAdder, but we've also made it available as a 
multi-platform, stand alone application using our popular DocBrowser 
technology found in our KDE Studio Gold product for C++ and Java 
development.

PyQtDoc has over 10mb of documentation in a clear and easy to read 
format. There are lots of examples, and a couple of tutorials. We will 
be keeping the documentation up to date with each release of Qt, however 
these updates are not free. You can buy each version as they come out 
for $19.95, or you can subscribe to the annual program which gets you 
all the updates for a year, which have typically been between 4 and 7. 
This annual program is only $69.95.

* HTML cross referenced documentation.
* "Table of Contents" panel with classes/function listings for rapid
navigation.
* Quick search for class or functions names
* Bookmarks for rapidly jumping between items of interest.
* Classes and functions have different icons so you can easily see if the
class is a QObject or QWidget or if the function is a slot or signal, etc.
* Lot of examples
* Python cod in class descriptions and some functions
* Supports PyQt version 3.5


About theKompany.com

theKompany.com (www.thekompany.com) is a
California-based company with developer teams in North America and Europe.
theKompany.com fills a need in the Linux community for mass-marketed,
quality Linux software by producing developer tools and desktop
applications. theKompany.com's products are marketed both online and
through B&M channels such as Microcenter and Fry's Electronics. Visit 
http://www.thekompany.com for more information.


From stuff@nonpoint.mailzilla.net  Mon Mar 17 03:38:47 2003
From: stuff@nonpoint.mailzilla.net (Phil)
Date: 16 Mar 2003 19:38:47 -0800
Subject: Kodos 1.0.0 released - a regular expression gui debugger for python
Message-ID: <mailman.1047908643.18571.clpa-moderators@python.org>

Kodos 1.0.0 has been released and is available at:

http://kodos.sourceforge.net

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 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.

Features new to version 1.0.0:

- Display in the "match tab" now automaticcaly scrolls to the selected
match number (eliminates need to scroll manually to find the match).

- Save File As dialog will now prompt if the selected file already
exists (allowing you to replace the existing file or select another
file).

To read more detailed information, view screenshots and download Kodos
please visit:  http://kodos.sourceforge.net


From aahz@pythoncraft.com  Mon Mar 17 15:54:22 2003
From: aahz@pythoncraft.com (Aahz)
Date: Mon, 17 Mar 2003 10:54:22 -0500
Subject: PyCon: Last week for pre-reg!
Message-ID: <mailman.1047917282.22768.clpa-moderators@python.org>

Friday, March 21 is the deadline if you want to get the $200
pre-conference price.  PyCon will cost $250 at the door, and there is no
single-day rate.

http://www.python.org/pycon/reg.html

PyCon DC 2003

   The first PyCon will be held 26-28 March, 2003, at George Washington
   University's Cafritz Conference Center in Washington DC. There will be
   a development sprint Mon/Tues before the conference.

   PyCon is a community-oriented conference targeting developers (both
   those using Python and those working on the Python project). It gives
   you opportunities to learn about significant advances in the Python
   development community, to participate in a programming sprint with
   some of the leading minds in the Open Source community, and to meet
   fellow developers from around the world. The organizers have worked
   hard to ensure that the conference be affordable and accessible to
   all. We look forward to seeing you there.
-- 
Aahz (aahz@pythoncraft.com)           <*>         http://www.pythoncraft.com/

Register for PyCon now!  http://www.python.org/pycon/reg.html

-- 
Aahz (aahz@pythoncraft.com)           <*>         http://www.pythoncraft.com/

Register for PyCon now!  http://www.python.org/pycon/reg.html


From jeremy@zope.com  Mon Mar 17 23:34:04 2003
From: jeremy@zope.com (Jeremy Hylton)
Date: 17 Mar 2003 18:34:04 -0500
Subject: ZODB4 alpha 1 release
Message-ID: <mailman.1047945064.6123.clpa-moderators@python.org>

We've released ZODB4 alpha 1, the first official release of the ZODB
code from the Zope3 project.  You can get it at
http://www.zope.org/Products/ZODB4.

This release contains essentially the same software that will be in the
upcoming Zope3 milestone release.  This version of ZODB is very
different from ZODB3.  The Persistent base class is a new-style class,
allowing persistent objects to use many of the features of Python 2.2
new-style classes.

There are still many changes planned for future versions of ZODB4, but
the current release is stable enough to call an alpha.  The current test
suite passes with Python 2.2.2 and Python 2.3 CVS on both Linux and
Windows (2k).  It will be possible to migrate data out of a 4.0a1
database into some future version.

This release contains the top-level persistence, transaction, and zodb
packages, as well as zope.interface and zope.testing.  The
implementation depends on zope.interface, but only in fairly limited
way.  The zope.testing package is only used by a few unit tests.
The zodb package includes FileStorage, two storages based on BerkeleyDB,
and ZEO, a client-server protocol for ZODB.

Jeremy




From guido@python.org  Tue Mar 18 15:51:53 2003
From: guido@python.org (Guido van Rossum)
Date: Tue, 18 Mar 2003 10:51:53 -0500
Subject: A few more days to register for PyDon DC!
Message-ID: <mailman.1048002995.1999.clpa-moderators@python.org>

Coming Friday is the *last day* to register for PyCon DC online.
After that, the rates go up to $250, and you'll have to pay on-site.

http://www.python.org/pycon/

Speakers!  This applies to you too.

Already registered?  BOOK YOUR HOTEL ROOM NOW!  Late March is cherry
blossom time in DC, and hotels fill up quickly.  Ditto for flights.

We've already got over 200 attendees registered.  Don't miss it!

--Guido van Rossum (home page: http://www.python.org/~guido/)


From johnp@reportlab.com  Tue Mar 18 11:40:52 2003
From: johnp@reportlab.com (John Precedo)
Date: Tue, 18 Mar 2003 11:40:52 -0000
Subject: Python UK conference Wikki up
Message-ID: <mailman.1048090983.681.clpa-moderators@python.org>

A basic Wikki Wikki is up for the UK Python Conference at
http://server.reportlab.com/accu-2003/moin.cgi/FrontPage.

Could anyone who will be attending the conference please add their name to
the Attendees page?

This will be the place to discuss travel arrangements, sort out lifts and
ride shares etc. We also plan to have organisation of the various short
talks here.

And of course since it is a Wikki, if you think of something else that
should be included you can add it yourself.

--
John Precedo  (johnp@reportlab.com)    Developer
Reportlab Europe Ltd  (http://www.reportlab.com)



From falted@openlc.org  Tue Mar 18 20:46:04 2003
From: falted@openlc.org (Francesc Alted)
Date: Tue, 18 Mar 2003 21:46:04 +0100
Subject: ANNOUNCE: Pytables 0.4
Message-ID: <mailman.1048090984.682.clpa-moderators@python.org>

Announcing PyTables 0.4
-----------------------

I'm happy to announce the first beta release of PyTables. It is labelled
beta because it has been thoroughly tested, even in production environmen=
ts,
and it is getting fairly mature.

Besides, from now on, the API will remain mostly stable, so you can start
using PyTables now with the guarantee that your code will also work (well=
,
mostly ;-) in the future. The large amount of unit tests included in
PyTables will also ensure the backward compatibility as well as the quali=
ty
of future releases will remain at least as good as it is now (although
hopefully it should increase!).

What's new
-----------

- numarray objects (NumArray, CharArray and RecArray) supported

- As a consequence of a large internal code redesign (numarray is at
  the core of PyTables now), performance has been improved by a factor
  of 10 (see "How Fast Is It?" section)

- It consumes far less memory than previous version

- Support for reading generic HDF5 files added (!)

- Some bugs and memory leaks existing in 0.2 solved

- Updated documentation

- Added more unit tests (more than 200 now!)

What it is
----------

In short, PyTables provides a powerful and very Pythonic interface to
process table and array data.

Its goal is to enable the end user to manipulate easily scientific
data tables and Numerical and numarray Python objects in a persistent
hierarchical structure. The foundation of the underlying hierarchical
data organization is the excellent HDF5 library
(http://hdf.ncsa.uiuc.edu/HDF5).

A table is defined as a collection of records whose values are stored
in fixed-length fields. All records have the same structure and all
values in each field have the same data type.  The terms
"fixed-length" and strict "data types" seems to be quite a strange
requirement for an interpreted language like Python, but they serve a
useful function if the goal is to save very large quantities of data
(such as is generated by many scientific applications, for example) in
an efficient manner that reduces demand on CPU time and I/O resources.

Quite a bit effort has been invested to make browsing the hierarchical
data structure a pleasant experience. PyTables implements just two
(orthogonal) easy-to-use methods for browsing.

What is HDF5?
-------------

For those people who know nothing about HDF5, it is is a general
purpose library and file format for storing scientific data made at
NCSA. HDF5 can store two primary objects: datasets and groups. A
dataset is essentially a multidimensional array of data elements, and
a group is a structure for organizing objects in an HDF5 file. Using
these two basic constructs, one can create and store almost any kind of
scientific data structure, such as images, arrays of vectors, and
structured and unstructured grids. You can also mix and match them in
HDF5 files according to your needs.

How fast is it?
---------------

PyTables can write table records between 20 and 30 times faster than
cPickle and between 3 and 10 times faster than struct (it is a module
present in the Standard Library); and retrieves information around 100
times faster than cPickle and between 8 and 10 times faster than
struct.

When compared with SQLite (http://www.sqlite.org/), one of the fastest
(free) relational databases available, PyTables achieves between a 60%
and 80% the speed of SQLite during selects of dataset sizes that fit
in the O.S. filesystem memory cache. However, when those sizes does
not fit in the cache (i.e. when dealing with large amounts of data),
PyTables beats SQLite by a factor of 2 or even more (depending on the
kind of record selected), and its performance in this case is only
limited by the I/O speed of the disk subsystem.

Go to http://pytables.sourceforge.net/doc/PyCon.html#section4 for a
detailed description on the conducted benchmarks.

Platforms
---------

I'm using Linux as the main development platform, but PyTables should
be easy to compile/install on other UNIX machines. This package has
also passed all the tests on a UltraSparc platform with Solaris 7 and
Solaris 8. It also compiles and passes all the tests on a SGI
Origin2000 with MIPS R12000 processors and running IRIX 6.5.

If you are using Windows and you get the library to work, please let
me know.

An example?
-----------

At the bottom of this message there is some code that shows basic
capabilities of PyTables. You may also look at
http://pytables.sourceforge.net/tut/tutorial1-1.html and=20
http://pytables.sourceforge.net/tut/tutorial1-2.html
for online code.

Web site
--------

Go to the PyTables web site for downloading and more details:

http://pytables.sf.net/

Share your experience
---------------------

Let me know of any bugs, suggestions, gripes, kudos, etc. you may
have.

Have fun!

-- Francesc Alted
falted@openlc.org


*-*-*-**-*-*-**-*-*-**-*-*- Small code example  *-*-*-**-*-*-**-*-*-**-*-=
*-*
from tables import *

class Particle(IsDescription):
    identity =3D Col("CharType", 22, " ", pos =3D 0)  # character String
    idnumber =3D Col("Int16", 1, pos =3D 1)  # short integer
    speed =3D Col("Float32", 1, pos =3D 1)  # single-precision

# Open a file in "w"rite mode
fileh =3D openFile("objecttree.h5", mode =3D "w")
# Get the HDF5 root group
root =3D fileh.root

# Create the groups:
group1 =3D fileh.createGroup(root, "group1")
group2 =3D fileh.createGroup(root, "group2")

# Now, create a table in "group0" group
array1 =3D fileh.createArray(root, "array1", ["string", "array"], "String=
=20
array")
# Create 2 new tables in group1
table1 =3D fileh.createTable(group1, "table1", Particle)
table2 =3D fileh.createTable("/group2", "table2", Particle)
# Create the last table in group2
array2 =3D fileh.createArray("/group1", "array2", [1,2,3,4])

# Now, fill the tables:
for table in (table1, table2):
    # Get the record object associated with the table:
    row =3D table.row
    # Fill the table with 10 records
    for i in xrange(10):
        # First, assign the values to the Particle record
        row['identity']  =3D 'This is particle: %2d' % (i)
        row['idnumber'] =3D i
        row['speed']  =3D i * 2.
        # This injects the Record values
        row.append()

    # Flush the table buffers
    table.flush()

# Select actual data from table.
# on entries where TDCcount field is greater than 3 and pressure less tha=
n 50
out =3D [ x['identity'] for x in table.iterrows()
        if x['idnumber'] > 3 and 4 < x['speed'] < 10 ]

print out

# Finally, close the file (this also will flush all the remaining buffers=
!)
fileh.close()


From max@alcyone.com  Wed Mar 19 02:17:00 2003
From: max@alcyone.com (Erik Max Francis)
Date: Tue, 18 Mar 2003 18:17:00 -0800
Subject: ANN: discord 1.0 -- Python conversion of dates to Discordian
Message-ID: <mailman.1048090985.683.clpa-moderators@python.org>

Summary

    A simple module for converting dates from Gregorian to Discordian.


Overview

    This is a very simple module which allows for conversion from
    normal dates (via 'time.time', 'time.localtime', etc.) to
    Discordian dates (a silly made-up dating system that divides a
    year into five seasons of 73 days each).  The module can either be
    used as a standalone command line application (which prints the
    current date in Discordian form) or as a extension module.


Getting the software

    The current version of discord is 1.0.

    The latest version of the software is available in a tarball here:
    http://www.alcyone.com/pyos/discord/discord-latest.tar.gz.

    The official URL for this Web site is
    http://www.alcyone.com/pyos/discord/.


Requirements

    This module requires Python 2.0 or greater.


License

    This code is released under the GPL.

....


Release history

    - 1.0; 2003 Mar 18.  Initial release.

-- 
 Erik Max Francis / max@alcyone.com / http://www.alcyone.com/max/
 __ San Jose, CA, USA / 37 20 N 121 53 W / &tSftDotIotE
/  \ Nine worlds I remember.
\__/ Icelandic Edda of Snorri Sturluson
    Maths reference / http://www.alcyone.com/max/reference/maths/
 A mathematics reference.


From drifty@bigfoot.com  Wed Mar 19 06:25:28 2003
From: drifty@bigfoot.com (Brett C.)
Date: 18 Mar 2003 22:25:28 -0800
Subject: python-dev Summary for 2003-03-01 through 2003-03-15
Message-ID: <mailman.1048090986.685.clpa-moderators@python.org>

+++++++++++++++++++++++++++++++++++++++++++++++++++++
python-dev Summary for 2003-03-01 through 2003-03-15
+++++++++++++++++++++++++++++++++++++++++++++++++++++

This is a summary of traffic on the `python-dev mailing list`_ from
March 1, 2003 through March 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@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 thirteenth summary written by Brett Cannon (same number as
my predecessor, Michael Hudson  =).

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_ (else it is probably regular
expression syntax); 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.

.. _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
.. _last summary: http://www.python.org/dev/summary/2003-02-16_2003-02-28.html

.. contents::

======================
Summary Announcements
======================
As I am sure most readers of this summary know by now, I am going to
PyCon_.  This means that I will be occupied the whole last week of
this month.  I suspect python-dev traffic will be light since I
believe most of PythonLabs will be at Pycon and thus not working.  =) 
But still, I will be occupied myself and thus won't have a chance to
work on the summary until I come home.  This means you should expect
the next summary to be rather late.  I will get to it, though, at some
point.

And in case you haven't yet, register for PyCon_.

.. _PyCon: http://www.python.org/pycon/

===============================
`Ridiculously minor tweaks?`__
===============================
__ http://mail.python.org/pipermail/python-dev/2003-March/033962.html

Splinter threads:
    - `How long is your shopping tuple?
<http://mail.python.org/pipermail/python-dev/2003-March/033996.html>`__
    - `Tuples vs lists
<http://mail.python.org/pipermail/python-dev/2003-March/033981.html>`__
    - `Re: lists v. tuples
<http://mail.python.org/pipermail/python-dev/2003-March/034029.html>`__
    - `mutability <http://mail.python.org/pipermail/python-dev/2003-March/034057.html>`__

The original point of this thread was Jeremy Fincher finding out if
patches changing lists to tuples where the list was not mutated would
be accepted for a miniscule performance boost (the answer was no). 
But this wasn't the interesting knowledge that came out of this
thread.  This thread led to Guido stating his intended uses of tuples
and lists.

And you might be going, "lists are for mutable sequences of objects
while tuples are for immutable sequences of objects".  Well, that is
not what Guido thinks of lists and tuples (and don't feel bad if you
thought otherwise; Christian Tismer didn't even know what Guido had in
mind and Python does not exactly require you to agree with Guido on
this).  Turns out that tuples, in Guido's view of the world, are "for
heterogeneous data" and "list[s] are for homogeneous data"; "Tuples
are *not* read-only lists".

Guido spelled out his thinking on this in a later email.  He basically
said that he viewed lists as "a sequence of items of type X" while
tuples are more like "a sequence of length N with items of type X1,
X2, X3, ..."  This makes sense since lists can be sorted while tuples
can't; sorting on different types don't necessarily result in a
sequence sorted the way you think about it.

And if you are still having issues of wrapping your head around this,
just view tuples as structs and lists as arrays as in C.

This thread then led to another topic of comparisons_ in Python. 
Guido ended up mentioning how he wished == and != worked on all types
(with disparate types always being !=) while all of the other
comparisons only worked on similar types for the interpreter's default
comparison abilities.

This then led to Guido saying how he wished the __cmp__() magic method
and the cmp() built-in didn't exist.  This is because there are
currently two ways to do comparisons; __cmp__(), and then all of the
other rich comparison magic methods.  You can implement the same
functionality as __cmp__() using just __lt__() and __eq__().  There
can also be an unneeded performance penalty for __cmp__() since (using
the previously mentioned way of re-implementing __cmp__()) you might
have to do some unneeded comparisons when all you need is __eq__().

This discussion is still going on.

.. _comparisons: http://www.python.org/dev/doc/devel/ref/customization.html#l2h-91


===========================
`Capabilities in Python`__
===========================
__ http://mail.python.org/pipermail/python-dev/2003-March/033820.html

Splinter threads:
    - `Capabilities <http://mail.python.org/pipermail/python-dev/2003-March/033854.html>`__
    - `about candy <http://mail.python.org/pipermail/python-dev/2003-March/033986.html>`__

This is a continuation of a discussion covered in the `last summary`_.

This was *definitely* the thread from hell for this summary.  =)  It
is very long and there was confusion at multiple points over
terminology.  You have been warned.

Three things were constantly being discussed in this thread;
restricted execution, capabilities, and proxies.  We discuss them in
this order.

Restricted execution basically cuts out access to certain objects at
execution time.  Currently, if you replace the global __builtins__
with something other then what __builtin__.__dict__ has then you
enable restricted execution in Python.  This cuts off access to
built-in objects so as to prevent you from circumventing security code
by, for instance, importing the sys_ module so you can replace a
module's code in sys.modules.  Both capabilities and proxies are
worthless without restricted execution since they could be
circumvented without it.

Capabilities can be viewed as references or bound methods (but not
both at the same time, necessarily).  Security with capabilities is
done based on possession; if you hold a reference to an object you can
use that object without issue.  The distribution of capabilities
becomes the issue with this system.

Proxies are a wrapper around objects that restrict access to the
object.  This restriction extends all the way to the core; even core
code such as built-ins can't get access to parts of a proxied object
that it doesn't want any object to get a hold of.  The trick with
proxies is making them secure on their own since they get passed
around without worrying who gets it since it is the proxy that
provides security, not possession like with capabilities.  Two
examples of proxies are `Zope proxies`_ and mxProxy_.

There was talk of a PEP on all of this but one has not appeared yet;
it is currently being worked on by Ben Laurie, though.

.. _sys: http://www.python.org/dev/doc/devel/lib/module-sys.html
.. _Zope proxies: http://dev.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/TransitionToSecurityProxies
.. _mxProxy: http://www.egenix.com/files/python/mxProxy.html


=========
Quickies
=========

`Codec registry <http://mail.python.org/pipermail/python-dev/2003-March/033805.html>`__
    Gustavo Niemeyer asked someone to review a patch.

`Changes to logging in CVS
<http://mail.python.org/pipermail/python-dev/2003-March/033811.html>`__
    Vinay Sajip if someone checked-in changes to the logging_ package
could be rolled back since it broke compatibility with Python 1.5.2
which the logging package tries to keep (as mentioned in `PEP 291`_). 
The changes were removed.

.. _logging: http://www.python.org/dev/doc/devel/lib/module-logging.html
.. _PEP 291: http://www.python.org/peps/pep-0291.html

`__slots__ for metatypes
<http://mail.python.org/pipermail/python-dev/2003-March/033815.html>`__
    Christian Tismer asked Guido and the list to take a look at a
patch that would allow meta-types to have a __slots__.  The patch was
accepted and applied.

`new bytecode results
<http://mail.python.org/pipermail/python-dev/2003-March/033817.html>`__
    Damien Morton continues on his quest to get performance boosts
from fiddling with the eval loop contained in `ceval.c`_ and trying
out various opcode ideas.  It was pointed out that pystone_ is a good
indicator of how Zope_ will perform on a new box.  It was also stated
by Tim Peters that since it is such an atypical test that it helps to
make sure any improvements you make *really* do make an improvement. 
Damien also requested more people contribute statistical information
to Skip Montanaro's stat server (more info at
http://manatee.mojam.com/~skip/python/ ).

.. ceval.c: 
.. _pystone: 
.. _Zope: http://www.zope.org/

`module extension search order - can it be changed?
<http://mail.python.org/pipermail/python-dev/2003-March/033826.html>`__
    This was discussed in the `last summary`_.  Tim Peters mentioned
how he doesn't use linecache_ often and that it's printing out of date
info is not of any great use for tracebacks.

.. _linecache: http://www.python.org/dev/doc/devel/lib/module-linecache.html

`JUMP_IF_X opcodes <http://mail.python.org/pipermail/python-dev/2003-March/033823.html>`__
    Damien Morton, still on the prowl for better opcodes, suggested
introducing opcodes that combined branching opcodes and POP_TOP (which
pops the top of the interpreter stack)¬?and did the pop based on the
truth value of what was being tested.  Neal Norwitz suggested that
instead the branching instructions just always pop the stack.  But
then Raymond Hettinger came up with prediction macros that give a
great speed boost to loops and conditionals by checking if the next
opcode is one that normally follows the current opcode.  If it does,
it skips going through the eval loop for the next opcode, thus saving
on overhead.
    If all of this cool opcode stuff that Damien keeps doing interests
you, you will want to read `opcode.h`_, `ceval.c`_, and learn how to
use the dis_ module.

.. _opcode.h: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/python/python/dist/src/Include/opcode.h
.. _ceval.c: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/python/python/dist/src/Python/ceval.c
.. _dis: http://www.python.org/dev/doc/devel/lib/module-dis.html

`Fun with timeit.py <http://mail.python.org/pipermail/python-dev/2003-March/033826.html>`__
    A new module named timeit_ was added to the stdlib at the request
of Jim Fulton.  The module times the execution of code snippets. 
Guido timed the execution of going through a 'for' loop a million
times with interpreters from Python 1.3 up to the current CVS (2.3a2
with patches up to that point).  The result was that CVS was the
fastest by a large margin.

.. _timeit: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/python/python/dist/src/Lib/timeit.py

`Pre-PyCon sprint ideas
<http://mail.python.org/pipermail/python-dev/2003-March/033827.html>`__
    I asked the list to suggest ideas to sprint on at PyCon_.

`More Zen <http://mail.python.org/pipermail/python-dev/2003-March/033828.html>`__
    Words of wisdom from Raymond Hettinger that everyone should read. 
And if you have never read Raymond's `School of Hard Knocks`_ email
you owe yourself to stop whatever you are doing and read it **now**. 
I can personally vouch that email is right on the money; I have
experienced (or suffered, depending on your view =) every single thing
on that list sans writing a PEP (although writing the Summary is
starting to be enough writing to be equal =) .

.. _School of Hard Knocks:
http://mail.python.org/pipermail/python-dev/2002-September/028725.html

`xmlrpclib <http://mail.python.org/pipermail/python-dev/2003-March/033837.html>`__
: `xmlrpclib: Apology
<http://mail.python.org/pipermail/python-dev/2003-March/033847.html>`__
    Bill Bumgarner, the "hillbilly from the midwest of the US", asked
if the xmlrpclib_ module was being maintained.  The lesson was also
learned to not call Fredrick Lundh "Fred" on the list since Fred L.
Drake, Jr. tends to be associated with the name.  =)

.. _xmlrpclib: http://www.python.org/dev/doc/devel/lib/module-xmlrpclib.html

`httplib SSLFile broken in CVS
<http://mail.python.org/pipermail/python-dev/2003-March/033832.html>`__
    Something got broken and fixed.

`super() bug (?) <http://mail.python.org/pipermail/python-dev/2003-March/033846.html>`__
    Samuele Pedroni thought he may have found a bug with super() but
turned out it wasn't.

`test_popen broken on Win2K
<http://mail.python.org/pipermail/python-dev/2003-March/033857.html>`__
    Win2k does not like quoting of commands when there is no space in
the command as Tim Peters discovered.  There were discussions on how
to deal with this.  The suggestion of coming up with an sh-like syntax
that works on all platforms (like what tcl's exec command has) was
suggsted.

`Change in int() behavior
<http://mail.python.org/pipermail/python-dev/2003-March/033863.html>`__
    David Abrahams rediscovered the joys of the road to which leads to
int/long unification when he noticed that
``isinstance(int(sys.maxint*2), int)`` returns False.  This will not
be an issue once we are farther down this road.

`acceptability of asm in python code?
<http://mail.python.org/pipermail/python-dev/2003-March/033868.html>`__
    Damien Morton popped his optimizing head back up on python-dev
asking if assembly code was acceptable in the core.  As of right now
there is none, but Tim Peters stated that if there was some that had
"a huge speedup, on all programs" then it would be considered,
although "on the weak end of maybe".  Christian Tismer (who plays with
assembly in Stackless_) warned against it because it could cause a
compiler to not use optimizations.

.. _Stackless: http://www.stackless.com/

`Internationalizing domain names
<http://mail.python.org/pipermail/python-dev/2003-March/033869.html>`__
    Martin v. L??wis asked someone to look over his patches to
implement IDNA (International Domain Names in Applications) which
allows non-ASCII characters in domain names.

`VERSION in getpath.c
<http://mail.python.org/pipermail/python-dev/2003-March/033882.html>`__
    Guido explains to someone what compile variables are used to
generate some compile-based search paths.

`Where is OSS used? <http://mail.python.org/pipermail/python-dev/2003-March/033905.html>`__
    Greg Ward asked what OSs use OSS_.

.. _OSS: http://www.opensound.com/ossfree/

`Audio devices <http://mail.python.org/pipermail/python-dev/2003-March/033947.html>`__
    Greg Ward asked for opinions on some API issues for ossaudiodev_.

.. _ossaudiodev: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/python/python/dist/src/Modules/ossaudiodev.c

`bsddb3 test errors - are these expected?
<http://mail.python.org/pipermail/python-dev/2003-March/033961.html>`__
    Skip Montanaro asked if some errors from the testing of bsddb3_ on
OS X were expected.

.. _bsddb3: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/python/python/dist/src/Modules/_bsddb.c

`os.path.dirname misleading?
<http://mail.python.org/pipermail/python-dev/2003-March/033980.html>`__
    Kevin Altis was surprised to discover that `os.path.dirname`_
would return the tail end of a directory instead of an empty string
when the argument to the function was just a directory name.

.. _os.path.dirname:
http://www.python.org/dev/doc/devel/lib/module-os.path.html#l2h-1443

`Care to sprint on the core at PyCon?
<http://mail.python.org/pipermail/python-dev/2003-March/033999.html>`__
    Me asking the world if they wanted to sprint on the core at the
pre-PyCon sprint (if you do, read the email for details).

`Iterable sockets? <http://mail.python.org/pipermail/python-dev/2003-March/034038.html>`__
    Andrew McNamara wished that socket objects were iterable on a
per-line basis without having to call makefile().  Guido said he would
rather come up with a better abstraction for Python 3 and prototype it
in Python 2.4 or later.

`More int/long integration issues
<http://mail.python.org/pipermail/python-dev/2003-March/034019.html>`__
    David Abrahams noticed that range() and xrange() couldn't accept a
long.  It basically led to Guido stating he considers xrange() a
mistake and wished it didn't exist now that we have iterators.  But
since getting rid of it would break code he can at least prevent it
from gaining abilities.  It also led to Guido mentioning again how he
would like to prohibit shadowing of built-ins.

`tzset <http://mail.python.org/pipermail/python-dev/2003-March/034062.html>`__
    A new function, time.tzset(), was added to Python and the tests
had failed under Windows.  The tests and the ./configure check were
changed as needed.

`PyObject_New vs PyObject_NEW
<http://mail.python.org/pipermail/python-dev/2003-March/033970.html>`__
    Lesson of the thread: PyObject_NEW is only to be used in the core;
use `PyObject_New()`_ for extension modules.

.. _PyObject_New(): http://www.python.org/dev/doc/devel/api/allocating-objects.html

`are NULL checks in Objects/abstract.c really needed?
<http://mail.python.org/pipermail/python-dev/2003-March/034011.html>`__
    ... They are not required, but they are there to protect you
against poorly written extensions.  Skip Montanaro subsequently
suggested a --without-null-checks compile option.

`PyEval_GetFrame() revisited
<http://mail.python.org/pipermail/python-dev/2003-March/034052.html>`__
    A possible API for manipulating the current frame was still being
discussed.


From europython@python.org  Wed Mar 19 12:52:02 2003
From: europython@python.org (europython@python.org)
Date: 19 Mar 2003 12:52:02 +0000
Subject: Call for Participation: EuroPython 2003
Message-ID: <mailman.1048090987.686.clpa-moderators@python.org>

The EuroPython Conference 2003 (EPC2003) returns to Belgium this June,
and the conference organizers are now accepting proposals for
presentations and tutorials.  We expect this year to be even more
successful, and we're not just talking about the Chimay.

We are looking for participation in the following conference tracks:
Python Frameworks, Python Language, Python in Business, Python in
Science and Industry, and Zope.  Track descriptions are available at
<http://www.europython.org/sessions/descriptions>.  The deadline for
submissions is Monday, April 21.

You can propose a 30 minute talk, a 45 minute talk, or a 2 hour
tutorial.  To propose a talk or tutorial, please visit the Talk
Submission page at <http://www.europython.org/Talks/callFor>.

For more information about the conference tracks, please contact the
track chairpersons listed at
<http://www.europython.org/sessions/descriptions>.  For general
questions about the conference, please visit the conference website at
<http://www.europython.org/>.  Also, if you would like to help us make
this year's EuroPython conference another success, please volunteer!
You can join us on the EuroPython mailing list at
<http://mail.python.org/mailman/listinfo/europython>.

About EuroPython Conference 2003:

  EuroPython Conference 2003 is the premiere venue for meeting Python
  and Zope developers from Europe and beyond.  As one of the first
  community-organized Python and Zope conferences, the EuroPython
  Conference delivers the atmosphere and information developers want.
  The conference will be held June 25-27, 2003 in Charleroi, Belgium.
  Information is available at the EuroPython website at
  <http://www.europython.org/>.  For more information, contact
  <info@europython.org>.



From pmagwene@speakeasy.net  Thu Mar 20 06:06:35 2003
From: pmagwene@speakeasy.net (Paul M)
Date: Thu, 20 Mar 2003 01:06:35 -0500
Subject: ANN: Java-to-Jython Browser
Message-ID: <mailman.1048172883.5879.clpa-moderators@python.org>

Description
------------
I've created a little app for browsing Java classes and querying their
events, bean properties, and methods as seen from Jython.  It's based on 
some example code from Richard Hightower's book "Python Programming with 
the Java Class Libraries" combined with a GUI that makes it easy to use.

Since I'm inexperienced with the Swing API, I've found this to be a 
particularly useful tool for learning how to build Swing-based GUIs from 
Jython.

Download
--------

http://kim.bio.upenn.edu/~pmagwene/java2jython.html

Contact
-------
Feedback, recommendations, and constructive critique are appreciated. 
Send email comments to p.magwene@snet.net

Cheers,
Paul



From aahz@pythoncraft.com  Thu Mar 20 17:41:48 2003
From: aahz@pythoncraft.com (Aahz)
Date: Thu, 20 Mar 2003 12:41:48 -0500
Subject: PyCon: One more day for pre-reg!
Message-ID: <mailman.1048182542.4013.clpa-moderators@python.org>

Friday, March 21 is the deadline if you want to get the $200
pre-conference price.  PyCon will cost $250 at the door, and there 
is no single-day rate.

http://www.python.org/pycon/reg.html

PyCon DC 2003

   The first PyCon will be held 26-28 March, 2003, at George Washington
   University's Cafritz Conference Center in Washington DC. There will be
   a development sprint Mon/Tues before the conference.

   PyCon is a community-oriented conference targeting developers (both
   those using Python and those working on the Python project). It gives
   you opportunities to learn about significant advances in the Python
   development community, to participate in a programming sprint with
   some of the leading minds in the Open Source community, and to meet
   fellow developers from around the world. The organizers have worked
   hard to ensure that the conference be affordable and accessible to
   all. We look forward to seeing you there.
-- 
Aahz (aahz@pythoncraft.com)           <*>         http://www.pythoncraft.com/

Register for PyCon now!  http://www.python.org/pycon/reg.html


From dave@boost-consulting.com  Thu Mar 20 18:25:59 2003
From: dave@boost-consulting.com (David Abrahams)
Date: Thu, 20 Mar 2003 13:25:59 -0500
Subject: [ANN] Version 1.30.0 of the Boost libraries
Message-ID: <mailman.1048199208.8713.clpa-moderators@python.org>

Boost version 1.30.0 has been released. The highlights include:

* Updates for Boost.Python, including better support for C++
  polymorphism, and introducing Pyste, a front-end wrapping code
  generator which allows most C++ code to be wrapped entirely using
  Python. (http://www.boost.org/libs/python/doc/news.html)

* Filesystem Library added - Portable paths, iteration over
  directories, and other useful filesystem operations, from Beman
  Dawes.

* Optional Library added - A discriminated-union wrapper for optional
  values, from Fernando Cacciola.

* Interval Library added - Extends the usual arithmetic functions to
  mathematical intervals, from Guillaume Melquiond, Herv=E9 Br=F6nnimann
  and Sylvain Pion.

* MPL added - Template metaprogramming framework of compile-time
  algorithms, sequences and metafunction classes, from Aleksey
  Gurtovoy.

* Spirit Library added - An LL (unlimited lookahead) parser framework
  that represents parsers directly as EBNF grammars in inlined C++
  source code, complete with semantic actions, ASTs and much more,
  from Joel de Guzman and team.

* Smart Pointers Library - many enhancements, intrusive_ptr and smart
  pointer programming techniques docs added.

* boost/assert.hpp, boost/current_function.hpp,
  boost/throw_exception.hpp, boost/checked_delete.hpp have been
  documented.

* Date-Time Library - several fixes and small additions including an
  interface change to partial_date.

* Function Library - added support for assignment to zero (to clear)
  and comparison against zero (to check if empty).

* Operators Library - now takes advantage of named return value
  optimization (NRVO) when available, from Daniel Frey.

* Regression Tests - Much expanded, plus a very nice summary page from
  Rene Rivera.

* Test Library - added new facilities.

* Many fixes and enhancements to other libraries.

See www.boost.org for more information.

--=20
Dave Abrahams
Boost Consulting
www.boost-consulting.com


From mary-python@puzzling.org  Fri Mar 21 02:06:03 2003
From: mary-python@puzzling.org (Mary Gardiner)
Date: Thu, 20 Mar 2003 21:06:03 -0500
Subject: Sydney, Australia: Python Interest Group: Monday 24th March
Message-ID: <mailman.1048248245.7333.clpa-moderators@python.org>

Hi everyone,

The Sydney Python Interest Group is on this Monday. Apologies that I've
been a week late getting it off the ground.

This month, Malcolm Tredinnick will talk about "Python in Production
Environments", in particular, things that come up in business scenarios
that aren't obvious from comp.lang.python or even Open Source projects.

The talk will have some technical content and a bunch of "lessons
learnt" and generalisations.

  Date: Monday March 24th (this Monday)

  Time: 7:00pm

  Location: University of Technology, Sydney (UTS) Broadway campus,
  building 10, room 2.440 (computer lab, on the entrance level). 

----

Sydney Python Interest Group meetings are announced on:

 - comp.lang.python.announce and python-announce-list@python.org[0]

 - the Australasian Python users list[1]

 - The Sydney Linux User's Group announce list[2]

[0] http://mail.python.org/mailman/listinfo/python-announce-list
[1] http://starship.python.net/mailman/listinfo/python-au
[2] http://lists.slug.org.au/listinfo/announce/

----

The Sydney Python Interest Group is, while not restricted to Python on
Linux, a Special Interest Group of the Sydney Linux Users Group (SLUG),
and would like to thank SLUG for its support.

See the PIG webpage: http://pig.slug.org.au/ for previous talks.



From guido@python.org  Fri Mar 21 12:01:03 2003
From: guido@python.org (Guido van Rossum)
Date: Fri, 21 Mar 2003 07:01:03 -0500
Subject: PyCon DC: last day for on-line registration
Message-ID: <mailman.1048248246.7334.clpa-moderators@python.org>

This is the final reminder that today (Friday) is the last day
to register online for PyCon DC.  Still only $200!  The conference
starts next Wednesday (March 26):

  http://www.python.org/pycon/

After today, you'll have to pay $250 on-site (credit cards only).

--Guido van Rossum (home page: http://www.python.org/~guido/)


From johnp@reportlab.com  Fri Mar 21 13:06:42 2003
From: johnp@reportlab.com (John Precedo)
Date: Fri, 21 Mar 2003 13:06:42 -0000
Subject: [ANN]  2003 Python UK Conference
Message-ID: <mailman.1048253502.23359.clpa-moderators@python.org>

Announcement of the 2003 Python UK Conference
=============================================

The UK Python conference 2003 will take place in Oxford, on Wednesday
April 2nd and Thursday 3rd. The conference will be held in the
pleasant surroundings of

Holiday Inn Oxford
Pear Tree Roundabout,
Woodstock Road,
Oxford, OX2 8JD
www.holiday-inn.co.uk

We are very excited to be working once again with the ACCU to bring
the UK Python conference to life. The conference last year was a big
success with all attendees, and we hope to repeat that success with a
bigger and better line up of speakers, including the Python language
founder Guido van Rossum, who will deliver the keynote on Wednesday
2nd April.

Other speakers include:
Alex Martelli, Andy Todd, Andy Robinson, Anthony Eden, Chris Withers,
Duncan Booth, Duncan Grisby, Greg Colvin, Hamish Lawson, Jacob
Hallén, Marc-André Lemburg, and Paul Brian.

As a taster of the conference we have conducted a series of short
interviews with Python luminaries including Guido van Rossum and Eric
Raymond. The interviews will be appearing on the conference website.

Conference website:
http://www.python-uk.org/

Conference Wiki:
http://server.reportlab.com/accu-2003/moin.cgi/

To sign up please go to here:
http://www.accuconference.co.uk/registration2003.asp

And to view the schedule, please go here:
http://www.shiningrose.co.uk/pyuk/pyukSchedule_current.html

--
John Precedo  (johnp@reportlab.com)    Developer
Reportlab Europe Ltd  (http://www.reportlab.com)




From altis@semi-retired.com  Fri Mar 21 18:14:56 2003
From: altis@semi-retired.com (Kevin Altis)
Date: Fri, 21 Mar 2003 10:14:56 -0800
Subject: ANN: Registration for Python 11 - OSCON 2003
Message-ID: <mailman.1048278187.6986.clpa-moderators@python.org>

The registration page for Python 11 at OSCON 2003 is now available. The
conference takes place July 7 - 11, 2003 in Portland, Oregon, USA.

  http://conferences.oreillynet.com/pub/w/23/register.html

The theme of OSCON this year is "Embracing and Extending Proprietary
Software".

The O'Reilly Open Source Convention brings together the leaders of more than
nine critical open source technologies. You will get an inside look at how
to configure, optimize, code, and manage these powerful tools. The
convention is rooted in a single premise -- to provide high-quality
information that will allow you to raise your level of expertise and
overcome challenges quickly, efficiently, and elegantly.

The conference sessions, including the Python tutorials (Monday, Tuesday)
and presentations (Wednesday, Thursday, Friday) are available at:

  http://conferences.oreillynet.com/pub/w/23/tutorial_python.html

  http://conferences.oreillynet.com/pub/w/23/track_python.html

  http://conferences.oreillynet.com/pub/w/23/tutorials.html

  http://conferences.oreillynet.com/pub/w/23/sessions.html

OSCON Home page:

  http://conferences.oreillynet.com/os2003/

I will repeat this announcement, provide additional information, and post
updates at least once a month between now and July.

ka
---
Kevin Altis - Python 11 co-chair
altis@semi-retired.com
http://radio.weblogs.com/0102677/



From barry@python.org  Fri Mar 21 21:38:18 2003
From: barry@python.org (Barry Warsaw)
Date: 21 Mar 2003 16:38:18 -0500
Subject: RELEASED email package version 2.5
Message-ID: <mailman.1048284603.12716.clpa-moderators@python.org>

--=-8ouReHRSbH1ne7hWcDtS
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

I've just released the (standalone) email package version 2.5.  This is
identical to the version that is in the current cvs development tree for
Python 2.3.  I've also backported it to what will be Python 2.2.3.

email 2.5 is made available as a distutils package for installing in
earlier versions of Python.  It is compatible with Python 2.1
Python 2.2, and Python 2.3.  See below for a summary of changes.

The email package is a library for parsing, handling, and generating
email messages and other RFC 2822 style documents.  It conforms to
most of the email related RFCs including 2045-2047 (the MIME RFCs) and
2231.  It is intended to replace several older modules in the standard
distribution, such as rfc822, mimetools, multifile, mimify, and
MIMEWriter, and such non-standard modules as mimecntl.

email-2.5.tar.gz is available from the mimelib project on SourceForge:

    http://sf.net/projects/mimelib

More information, as well as on-line documentation is available on the
home page:

    http://mimelib.sf.net

Enjoy,
-Barry

-----snip snip-----
    - Message.get_payload() now recognizes various uuencoded
      Content-Transfer-Encodings (e.g. x-uuencode).

      When passing decode=3DTrue to Message.get_payload() and a
      low-level decoding error occurs, the payload is returned as-is
      instead of raising an exception.

    - Header.__init__() and Header.append() now accept an optional
      argument `errors' which is passed through to the unicode() and
      ustr.encode() calls.  You can use this to prevent conversion
      errors by e.g. passing 'replace' or 'ignore'.

      RFC 2822 specifies that long headers should be split at the
      "highest level syntactic break" possible.  This can only really
      be determined by the application, and the current API doesn't
      support arbitrary break points.  As a compromise,
      Header.encode() grew a `splitchars' argument which provides some
      control over splitting at higher level syntactic breaks.

      Header.decode_header() now transforms binascii.Errors into
      email.Errors.HeaderParseErrors when bogus base64 data appears in
      the header.

      The header splitting and folding algorithms were completely
      reimplemented, especially when dealing with ASCII headers.

      We now preserve spaces between encoded and non-encode parts in
      RFC 2047 headers when converting the header to Unicode.  While
      the RFC is technically ambiguous on this point, this is the
      behavior most people expect.

    - email.Iterators.body_line_iterator() now takes an optional
      decode argument, which is passed through to Message.get_payload().

    - The MIMEText constructor used to append a newline to the _text
      argument if it didn't already end in a newline.  Now it doesn't.

    - The quopriMIME.header_encode() maxlinelen argument now accepts
      None, which inhibits line breaking.

    - Support for Korean charsets was added to Charset.py.  Also the
      Charset class grew a __repr__() method.

    - Various and sundry bug fixes, improved RFC conformance, and
      improved lax parsing.


--=-8ouReHRSbH1ne7hWcDtS
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iQCVAwUAPnuGSXEjvBPtnXfVAQIfwgQAp3X4Z3CVh0WoHm5hayLh8rQ4TWdn0xfR
G4yoBUX3fwziL+cbOtdufZ17nGv4FhQfRX6A4ziFTE3TO3GywVBeUWaEiPqBoDGm
ZuKo59tBE/tbfddM8ZFJVvkTDTXsGD9sIymU97ZSKFqkhuDAC0FGr5C/ELMHSJuT
pZJXUUPGwts=
=vFHf
-----END PGP SIGNATURE-----

--=-8ouReHRSbH1ne7hWcDtS--



From dave@boost-consulting.com  Sun Mar 23 04:22:00 2003
From: dave@boost-consulting.com (David Abrahams)
Date: Sat, 22 Mar 2003 23:22:00 -0500
Subject: [ANN]  2003 Python UK Conference
References: <mailman.1048253502.23359.clpa-moderators@python.org>
Message-ID: <mailman.1048422602.2798.clpa-moderators@python.org>

"John Precedo" <johnp@reportlab.com> writes:

> Other speakers include:
> Alex Martelli, Andy Todd, Andy Robinson, Anthony Eden, Chris Withers,
> Duncan Booth, Duncan Grisby, Greg Colvin, Hamish Lawson, Jacob
> Hall=E9n, Marc-Andr=E9 Lemburg, and Paul Brian.

...and if you care about Python/C++ interoperability and can bear to
hang around 'till Friday afternoon I'll be giving a Boost.Python talk.
For some strange reason the ACCU organizers decided not to schedule
this talk during the Python part of the program.

--=20
Dave Abrahams
Boost Consulting
www.boost-consulting.com


From jjl@pobox.com  Sun Mar 23 13:08:38 2003
From: jjl@pobox.com (John J Lee)
Date: Sun, 23 Mar 2003 13:08:38 +0000
Subject: RELEASE: ClientForm 0.0.7
Message-ID: <mailman.1048454282.1642.clpa-moderators@python.org>

http://wwwsearch.sourceforge.net/ClientForm/

Changes since 0.0.5:
 * Empty TEXTAREA case fixed.
 * Exception is no longer raised for INPUT TYPE=FILE -- instead, FILE
   controls are just ignored (they will be handled properly in 0.1.x).
 * Documentation improvements to web page (note that the web page is
   more up to date than the copy of same in the package -- sorry).

Requires Python >= 1.5.2.

ClientForm is a Python module for handling HTML forms on the client
side, useful for parsing HTML forms, filling them in and returning the
completed forms to the server.  It has developed from a port of Gisle
Aas' Perl module HTML::Form, from the libwww-perl library, but the
interface is not the same.

Simple example:

 from urllib2 import urlopen
 from ClientForm import ParseResponse

 forms = ParseResponse(urlopen("http://www.acme.com/form.html"))
 first_form = forms[0]
 form["author"] = "Gisle Aas"

 # form.click returns a urllib2.Request object
 # (use the items argument to this method if you're not using urllib2)
 response = urlopen(form.click("Thanks"))


John



From sholden@holdenweb.com  Sun Mar 23 17:16:34 2003
From: sholden@holdenweb.com (Steve Holden)
Date: Sun, 23 Mar 2003 12:16:34 -0500
Subject: Invitation to PyCon
Message-ID: <mailman.1048454283.1704.clpa-moderators@python.org>

Well, looks like it's PyCon weekend in DC, folks, and here we are amid the
cherry blossom (sadly not a feature of this year's cherry blossom festival).

The registrations have been smoothly handled by our colleagues of Yet
Another Society, for which we thank them. Those who have had to request a
refund should expect a formal response shortly before or after PyCon ends.
If you do not receive such a response by email, please contact me to ensure
your details have been received.

I look forward to putting faces to many names, and extend the hand of
friendship to all pythonistas, whether attending PyCon or not.

There's a goodly crowd attending, barring any travel-related problems such
as weather (which featured in my missing the first Python conference I
booked). The sprinters are already converging to begin work on Monday, and
if you aren't sprinting then think about coming in on TUESDAY AFTERNOON to
register early and avoid the morning rush on Wednesday.

PyCon's organizers are all interested in hearing your feedback on the
conference, and this will be the theme of a session late in the agenda,
where your feedback (negative and, hopefully, ;positive)can be made more
publicly.

Over all we are trying to provide an interesting week with access to Python
talent, humor, conceit, and all else that we consider positive about the
language. If you aren't already registered then it will cost you $250 at the
door (again, if you want to register AT THE CONFERENCE we recommend that you
register ON SITE TUESDAY AFTERNOON with your credit card).

There has apparently been a good response to our call for gophers, and I'd
like to thank all our volunteer gophers in advance for helping to keep the
wheels rolling.

Ladies and gentlemen, welcome to PyCon DC 2003 week
--
Steve Holden                                  http://www.holdenweb.com/
Python Web Programming                 http://pydish.holdenweb.com/pwp/
Register for PyCon Tuesday March 25  at GWU's Cafritz Conference Center







From peter@engcorp.com  Mon Mar 24 00:40:13 2003
From: peter@engcorp.com (Peter Hansen)
Date: Sun, 23 Mar 2003 19:40:13 -0500
Subject: Toronto-area Python/Zope user group meets Tuesday March 25
Message-ID: <mailman.1048467122.23076.clpa-moderators@python.org>

This is the second and final notice about the next PyGTA
meeting, which will take place on Tuesday March 25 at
eight o'clock in the evening at the usual location.

Details are in our web page at http://web.engcorp.com/pygta .

We look forward to seeing everyone who comes out!

-Peter Hansen and Ian Garmaise, PyGTA organizers


From jure@aufbix.org  Tue Mar 18 18:45:04 2003
From: jure@aufbix.org (Jure Koren)
Date: Tue, 18 Mar 2003 13:45:04 -0500 (EST)
Subject: [Module] md5_crypt/1.0
Message-ID: <mailman.1048617198.2482.clpa-moderators@python.org>

                             md5_crypt/1.0                              
                             -------------                              

md5crypt, password hashing algorithm

A very common algorithm for hashing passwords on modern unices (the kind
your favourite linux distribution uses). Implemented in C for speed,
wrapped in python for convenience.


       URL:  http://aufbix.org/~i/python/
  Download:  http://aufbix.org/~i/python/md5_crypt-0.1.tar.gz

   License:  Public Domain
  Platform:  *nix

  Categories:  Encryption/Encoding

Jure Koren (jure@aufbix.org)
http://aufbix.org/~i/python/

--
<a href="http://aufbix.org/~i/python/">md5_crypt/1.0</a> -- md5crypt,
password hashing algorithm



From greg@cosc.canterbury.ac.nz  Thu Mar 27 06:23:29 2003
From: greg@cosc.canterbury.ac.nz (Greg Ewing (using news.cis.dfn.de))
Date: Thu, 27 Mar 2003 18:23:29 +1200
Subject: ANN: Pyrex 0.6
Message-ID: <mailman.1048791485.7076.clpa-moderators@python.org>

Pyrex 0.6 is now available:

    http://www.cosc.canterbury.ac.nz/~greg/python/Pyrex/

There are several new features in this release:

   - Command line options for reporting version number,
     requesting a listing file and specifying the name of
     the generated C file.

   - An 'include' statement for including other Pyrex files.

   - Improved facilities for exporting declarations from
     one Pyrex file to another.

   - Python syntax compatibility enhancements: try-except-else,
     multiple statements on one line.

   - A __delete__ special method has been added to extension
     types (invoked when using del on an attribute).

There is one backward-incompatible change that you should
note:

   - C character literals now have a distinct syntax: c'X'
     (the automatic coercion of char * to char that Pyrex
     did before proved to be too error-prone and has been
     removed).

There are also some other minor improvements and a slew
of bug fixes -- see the CHANGES file for a full list.


What is Pyrex?
--------------

Pyrex is a new language for writing Python extension modules.
It lets you freely mix operations on Python and C data, with
all Python reference counting and error checking handled
automatically.

-- 
Greg Ewing, Computer Science Dept,
University of Canterbury,	
Christchurch, New Zealand
http://www.cosc.canterbury.ac.nz/~greg



From g_will@cyberus.ca  Wed Mar 26 21:16:21 2003
From: g_will@cyberus.ca (Gordon Williams)
Date: Wed, 26 Mar 2003 16:16:21 -0500
Subject: [ANN] wxPyPlot V1.0 Beta
Message-ID: <mailman.1048791483.6908.clpa-moderators@python.org>

Hi All,

I have released Version 1.0 beta of wxPyPlot for producing simple plots
in wxPython.  Since the alpha3 release I have optimized the speed for
markers
and fixed a small bug in location in the y-axis label.

For your viewing pleasure, the website now has some html docs as well as a
few more screen shots of things.  Check out:
http://www.cyberus.ca/~g_will/wxPython/wxpyplot.html

Comments and suggestions welcome.

Regards,

Gordon Williams

-------------------------------------------------------------
What is wxPyPlot??

wxPyPlot is an enhanced derivative version of wxPlotCanvas to provide simple
lightweight plotting in wxPython. The emphasis is both on simple and
lightweight.

Before starting this work I looked at two plotting packages that could be
adapted to work with wxPython. SciPy Plt and Chaco are sophisticated and
powerful, but at the expense of consuming huge amounts of computer resources
for simple plots. They can be found at http://scipy.com. I was looking for
something that could be incorporated into a Boa application and had the
ability to plot lines with large numbers of points quickly for data capture
applications. wxPlotCanvas had the speed and some of the functionality that
I was looking for, but lacked a lot of features that I needed. This effort
has filled the gap.

Features:
- Automatic Scaling of Axes
- Legends for lines and markers
- Plot Title and Axis Labels
-  Zoom Region with Mouse (Rubber Band) or Programmatically
- Scroll Up/Down, Left/Right
- Plot Grid (Graticule) on Graph
- Printing, Preview, and Page Set-up (margins) -WYSIWYG
- Cursor X-Y User Axis Values
- Simple, Lightweight and Fast
- Can be Used with Boa Applications if Desired
- Lots of Comments and Doc Strings along with Example Usage

I have tested this out on Windows using Python 2.2 and wxPython 2.4.0.6. If
you have the chance to test it on Linux, please let me know how it works.
Suggestions and improvements welcome.

Screen shots, source and instructions for Boa can be found at

http://www.cyberus.ca/~g_will/wxPython/wxpyplot.html






From knight@baldmt.com  Fri Mar 28 13:34:16 2003
From: knight@baldmt.com (Steven Knight)
Date: Fri, 28 Mar 2003 07:34:16 -0600 (CST)
Subject: ANNOUNCE:  SCons 0.12 (build tool in Python) is now available
Message-ID: <mailman.1048861634.13198.clpa-moderators@python.org>

SCons is a software construction tool (build tool, or make tool) written
in Python.  It is based on the design which won the Software Carpentry
build tool competition in August 2000.

Version 0.12 of SCons has been released and is available for download
from the SCons web site:

	http://www.scons.org/

Or through the download link at the SCons project page at SourceForge:

	http://sourceforge.net/projects/scons/

RPM and Debian packages and a Win32 installer are all available, in
addition to the traditional .tar.gz and .zip files.


WHAT'S NEW IN THIS RELEASE?

IMPORTANT:  Release 0.12 contains the following interface changes:
  - SCons now changes to the directory in which an SConscript
    file resides while reading that SConscript file.

  See the release notes for more information about this change.

This release adds the following features:
  - Support has been added for fetching source files from the SCCS, RCS,
    CVS, Perforce and BitKeeper source code management systems.
  - A separate src_dir argument to SConscript() allows explicit
    specification of where source files can be found.
  - Current Builder-based command generators can be replaced by more
    flexible generators based on callable construction variables.
  - The Install() and InstallAs() builders now copy files.  This behavior
    is now configurable via the INSTALL construction variable.
  - SCons now issues a warning if you try to use the reserved variable
    names TARGET, TARGETS, SOURCE or SOURCES.
  - Builders for Tar and Zip files have been added.
  - SCons now supports an explicit Exit() function for terminating early.
  - The masm tool now supports SharedObject() builds.

This release removes the following deprecated features:
  - Builder objects no longer support a "name" argument.
  - The Environment.Update() method has been removed.

The following fixes have been added:
  - The string value of a File or Dir node now rturns a path
    relative to the calling SConscript file's directory, not the
    top-level directory.
  - Commands that expand the third or later argument from $TARGET,
    $TARGETS, $SOURCE or $SOURCES now calculate signatures properly.
  - Exceptions thrown by Scanners are no longer silently eaten.
  - A built file may no longer be pushed to a CacheDir() with a
    signature of None.
  - Built files are no longer copied to a CacheDir() if they're
    already there.
  - Files copied to a CacheDir() are now written to a temporary file
    and renamed, to avoid corrupt partial copies.
  - The -U option with no Default() targets no longer throws an exception.
  - The -u option, when used from a source directory with no local
    targets, will now build corresponding targets in any associated
    BuildDir()s.
  - The WhereIs() function now returns normalized path names.
  - An Aliased source that doesn't exist no longer generates an
    incorrect dependency-cycle error.

Performance has been improved as follows:
  - The internal to_String() function has been sped up.

The documentation has been improved:
  - Clearer explanation has been added of how to export variables to a
    subsidiary SConscript file.
  - Bugs in various Tool examples have been fixed.
  - The man page now correctly describes that the -f option doesn't
    change to the directory in which the SConstruct file lives.


ABOUT SCONS

Distinctive features of SCons include:

  - a global view of all dependencies; no multiple passes to get
    everything built properly
  - configuration files are Python scripts, allowing the full use of a
    real scripting language to solve difficult build problems
  - a modular architecture allows the SCons Build Engine to be
    embedded in other Python software
  - the ability to scan files for implicit dependencies (#include files);
  - improved parallel build (-j) support that provides consistent
    build speedup regardless of source tree layout
  - use of MD5 signatures to decide if a file has really changed; no
    need to "touch" files to fool make that something is up-to-date
  - easily extensible through user-defined Builder and Scanner objects
  - build actions can be Python code, as well as external commands

An scons-users mailing list is available for those interested in getting
started using SCons.  You can subscribe at:

	http://lists.sourceforge.net/lists/listinfo/scons-users

Alternatively, we invite you to subscribe to the low-volume
scons-announce mailing list to receive notification when new versions of
SCons become available:

	http://lists.sourceforge.net/lists/listinfo/scons-announce


ACKNOWLEDGEMENTS

Special thanks to Charles Crain, Lachlan O'Dea, Jeff Petkau and Anthony
Roach for their contributions to this release.

On behalf of the SCons team,

	--SK



From ahaas@airmail.net  Fri Mar 28 16:52:43 2003
From: ahaas@airmail.net (Art Haas)
Date: Fri, 28 Mar 2003 10:52:43 -0600
Subject: [ANNOUNCE] Fifth release of PythonCAD now available.
Message-ID: <mailman.1049047588.4745.clpa-moderators@python.org>

I'd like to announce the fifth release of PythonCAD, a CAD package
for open-source software users. As the name implies, PythonCAD is
written entirely in Python. The goal of this project is to create
a fully scriptable drafting program that will match and eventually
exceed features found in commercial CAD software. PythonCAD is released
under the GNU Public License (GPL).

PythonCAD requires Python 2.2. The interface is GTK 2.0 based,
and uses the PyGTK module for interfacing to GTK. The design of
PythonCAD is built around the idea of separating the interface
from the back end as much as possible. By doing this, it is hoped
that both GNOME and KDE interfaces can be added to PythonCAD through
usage of the appropriate Python module. Addition of other interfaces
will depend on the availability of a Python module for that particular
interface and developer interest and action.

The fifth release adds the first appearance of a global and user
preferences file. Dimensions can now display endpoint markers like
arrows and slashes, though the size these objects are displayed at
is currently fixed. This limitation should be removed in one of the
next two releases. The first implementation of leader lines has been
added as well. This release also has many internal changes in preparation
for adding hatching. There are also new methods for finding entities in
a drawing. Finally, the usual assortment of bug fixes and code tweaks
are included. By the way, a screenshot showing the dimension endpoints
and leader line has been added to the screenshot page at the web site.

In response to user feedback, drawing files are now saved with a '.gz'
extension. The files have always been saved in a compressed format, but
the name did not indicate this. With this change it should be more evident
that the PythonCAD files are not stored in an uncompressed format.

With this release I am also making a request for help in setting up
a mailing list. The lack of a mailing list for people interested in
working on PythonCAD to find one another and discuss development issues
is a hindrance in adding developers to the project. I do not have the
hardware or connection to set up a mailing list on my own, so I would
appreciate a few suggestions for sites willing to provide this service.

Visit the PythonCAD web site for more information about what PythonCAD
does and aims to be:

http://www.pythoncad.org

Come and join me in developing PythonCAD into a world class drafting
program!

Art Haas
-- 
They that can give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety.
 -- Benjamin Franklin, Historical Review of Pennsylvania, 1759


From mike@nthwave.net  Fri Mar 28 18:50:46 2003
From: mike@nthwave.net (Michael Mell)
Date: Fri, 28 Mar 2003 18:50:46 GMT
Subject: [Announce] Elements : for building web sites
Message-ID: <mailman.1049047590.4758.clpa-moderators@python.org>

I'm pleased to announce Elements 1.1.1.

Elements is a Python-based tool for building web sites. Elements source 
files are built in a simple and powerful structure that allows the 
developer to define components or "elements" such as templates, code 
fragments and Python scripts. The Elements application merges the 
appropriate pieces together to build html files on the developer's local 
file system.

Python scripts within Elements source files are fully aware of the file 
name, path and many Elements "environment variables" of each html file 
as it is processed. All elements are recognized hierarchically -- a 
site-wide element can be defined in multiple locations down and across 
the site hierarchy. Hierarchically-based elements, multiple templates 
and embedded Python code together provide a powerful system to build web 
sites.

The Elements application generates static html files, but Elements can 
help generate code for other processes. For example, PHP code can exist 
peacefully and benefit from being part of an Elements-built site.


Elements has been used to produce web sites for Fortune 500 clients, 
artists and small businesses.

Elements has been tested on Mac OS9, OSX, Linux Redhat 7 and Windows of 
various flavors.

Elements is donorware.

The source code is available for download.
http://www.nthwave.net/elements/


I'm particularly interested in feedback on the documentation, do the 
docs clearly describe what it does, and how to use it? Would screen 
grabs of Elements code help clarify the process?

I've done some work to extend Elements to the web server. In this 
scenario the developer(s) will edit Elements source files on the web 
server, and when ready, run the Elements process to create a new version 
of the site. If this sounds interesting or useful, please let me know.


From philh@cabalamat.org  Sun Mar 30 05:59:25 2003
From: philh@cabalamat.org (phil hunt)
Date: Sun, 30 Mar 2003 06:59:25 +0100
Subject: [ANN] Easibox 0.1.5 released
Message-ID: <mailman.1049047592.4821.clpa-moderators@python.org>

Easibox is a utility for making tar files, zip files and other
archive files, designed to be particularly useful when making
releases of open source projects.

Easibox was written to solve a problem I had when releasing
open source software packages, such as my Leafwa program. The
technique I was using was manually creating a directory with
the required filename (such as "leafwa-0.6.1"), copying those
files to be archived into the directory, and then cd'ing to
that directory's parent and running tar to create the tarball.
I found this process time-consuming and error-prone. So I
decided there must be a better way...

My solution was this program ``easibox'' which decides what
files it will put in the archive, what sort of archive files
will be created, and other parameters, based on the contents
of a configuration file in the project directory. The
configuration file is read in by the Python interpreter; this
means that it uses Python syntax (so you don't have to learn
another file type) and that you can put Python program
statements in it. 

Easibox is written in Python and licensed under the GNU
General Public License; see file COPYING (which comes with the
distribution) for details.

Easibox is available on the web at:
   <http://www.cabalamat.org/oss/easibox/intro.html>


-- 
Philip Hunt <philh@cabalamat.org>

Interested in adventure holidays in Spain? 
Look at: <http://www.cabalamat.org/advcon/>


From greg@cosc.canterbury.ac.nz  Mon Mar 31 03:16:51 2003
From: greg@cosc.canterbury.ac.nz (Greg Ewing (using news.cis.dfn.de))
Date: Mon, 31 Mar 2003 15:16:51 +1200
Subject: ANN: Pyrex 0.6.1 - distutuls extension fixed
Message-ID: <mailman.1049124363.31107.clpa-moderators@python.org>

It has been brought to my attention that the distutils
extension was broken in Pyrex 0.6.

Get 0.6.1 while it's hot:

http://www.cosc.canterbury.ac.nz/~greg/python/Pyrex/


What is Pyrex?
--------------

Pyrex is a new language for writing Python extension modules.
It lets you freely mix operations on Python and C data, with
all Python reference counting and error checking handled
automatically.

-- 
Greg Ewing, Computer Science Dept,
University of Canterbury,	
Christchurch, New Zealand
http://www.cosc.canterbury.ac.nz/~greg



From edream@tds.net  Mon Mar 31 14:35:59 2003
From: edream@tds.net (Edward K. Ream)
Date: Mon, 31 Mar 2003 14:35:59 GMT
Subject: ANN: leo.py 3.11 beta 4
Message-ID: <mailman.1049124365.31333.clpa-moderators@python.org>

leo.py 3.11 beta 4 is now available at: http://sourceforge.net/projects/leo/

This will be the last beta release before 3.11 final.

The highlights of beta 4:
-------------------------
- Fixed several minor problems with unicode.
- Fixed a _huge_ performance bug that slowed moving nodes left.
- Added several new plugins:
 - Support for the VIM editor.
 - A French translation of all menus.
- Added many minor bug fixes and improvements.

The highlights of 3.11:
-----------------------
** Leo now supports unicode properly.
 - New @encoding directives specifies encoding for derived files.
 - New settings specify default encodings for .leo and derived files.
 - Derived files specify encodings used to create them.
** A new plugin architecture for customizing Leo.
- New commands:
 - Toggle Angle Brackets.
 - Insert Time/Date (in headline or body text).
 - Go To First/Last Node, Parent, Next/Previous Sibling.
 - Write Missing @file Nodes.
 - Expand/Contract Node.
- Improved commands:
 - Expand/Contract commands now operate on the selected tree.
   ( A major improvement)
 - Sort Siblings command can now sort top-level nodes.
 - Leo now allows multiple writes of cloned nodes.
   (Useful when different @path directives are in effect.)
- Other improvements:
 - Improved syntax coloring for html and xml.
 - Leo scrolls partially visible headlines into full view.
 - Added "Replace tabs with spaces" checkbox in Prefs panel.
 - Added install script for Linux.
- New settings in leoConfig.leo/.txt.
 - Colors for Show Invisibles command and body_insertion_cursor
 - Settings affecting when control-drags start.
 - Defaults for unicode (see above).
- Many other bug fixes and improvements.

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.

leo.py requires Python 2.1 or above and tcl/tk 8.3 or above.
leo.py will work on Linux, Windows and MacOs X Jaguar.

Links:
------
Leo:      http://personalpages.tds.net/~edream/front.html
Home:     http://sourceforge.net/projects/leo/
Download: http://sourceforge.net/project/showfiles.php?group_id=3458
CVS:      http://sourceforge.net/cvs/?group_id=3458

Edward K. Ream
--------------------------------------------------------------------
Edward K. Ream   email:  edream@tds.net
Leo: Literate Editor with Outlines
Leo: http://personalpages.tds.net/~edream/front.html
--------------------------------------------------------------------



From chrism@zope.com  Mon Mar 31 16:46:32 2003
From: chrism@zope.com (Chris McDonough)
Date: 31 Mar 2003 11:46:32 -0500
Subject: Now online: Paper and Slides for "Application Configuration Using
 ZConfig"
Message-ID: <mailman.1049132413.25980.clpa-moderators@python.org>

Hi folks,

At PyCon DC last week, I presented a paper written by Fred Drake and
myself about ZConfig, a library which allows Python programmers to
retrieve, constrain and convert user-supplied configuration data.

The paper and the slides which presented the paper are now online for
your viewing pleasure:

http://www.zope.org/Members/mcdonc/Presentations

Enjoy!

- C