Mailman 3 May 2003 - Python-announce-list

EuroPython 2003: Call For Talks Extended
by Michael Hudson May 5, 2003

May 5, 2003

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 extended till Monday, May 12. If you haven't done so or are still hesitating, you can still propose a 30 minute talk, a 45 minute talk, or a 90- minute tutorial. To propose a talk or tutorial, please visit the Talk Submission page at <http://www.europython.org/Talks/callFor>. Starting now, if you don't have the time to prepare a full-length talk, we are also seeking people who want to give a 'Lightning Talk': a short (5 minute), focused talk about any Python- or Zope-related subject you fancy! 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/>. 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 <europython(a)python.org>.

1 0

[ANNOUNCE] Sixth release of PythonCAD now available
by Art Haas May 4, 2003

May 4, 2003

I'd like to announce the sixth 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 sixth release at long last adds the ability to store text in a drawing. The text handling is in its earliest stages of development, but now it is there. There is a new Polyline entity available to use in a drawing now. A Polyline is essentially the same thing as a connected set of segments, with the segments joined at the endpoint of one to another. The ability to mirror objects around an arbitrarily angled construction line has been added in this release as well. This release also has a large number of internal code cleanups. A large amount of code is being moved from the interface specific directory to the general directory. Doing so reduces the potential of code duplication in various interfaces. Another improvement in this release is a reworking of the code used when building or modifying entities through the menu choices. A new set of object classes has been added that are specific for the operation to be performed, and the use of these new classes makes the code to execute the operation simpler to add and understand. The usual amount of code cleanups, bug fixes, tweaks, and documentation additions have been done in this new release as well. Unfortunately there is still no mailing list for PythonCAD just yet. I want to find a site that will accept mail from anyone, not just list subscribers, filter the mail to remove the spam, then send the mail out to the subscribers. Lists on Sourceforge and the GNU Subversions site allow more spam than I want, so I am still looking for options. I cannot stress highly enough how I want the list to be free from junk mail that unfortunately ends up clogging so many mailing lists. So, I am still looking for recommendations about sites that can host the mailing list. 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 -- To announce that there must be no criticism of the President, or that we are to stand by the President, right or wrong, is not only unpatriotic and servile, but is morally treasonable to the American public. -- Theodore Roosevelt, Kansas City Star, 1918

1 0

ANN: PyObjC 0.9
by Ronald Oussoren May 4, 2003

May 4, 2003

PyObjC 0.9 is now available for download at http://pyobjc.sourceforge.net/ PyObjC is a bridge between Python and Objective-C. It allows full featured Cocoa applications to be written in pure Python. It is also easy to use other frameworks containing Objective-C class libraries from Python and to mix in Objective-C, C and C++ source. Python is a highly dynamic programming language with a shallow learning curve. It combines remarkable power with very clear syntax. The installer package includes a number of Project Builder templates for easily creating new Cocoa-Python projects. Version 0.9 also introduces support for sytax coloring of Python files in Project Builder. PyObjC also supports full introspection of Objective-C classes and direct invocation of Objective-C APIs from the interactive interpreter. PyObjC requires MacOS X 10.2 or later. PyObjC works both with the Apple provided Python installation in MacOS X 10.2 (and later) and with MacPython 2.3b1. Users of MacPython 2.3b1 can install PyObjC though the PackageManager application. PyObjC 0.9 includes many inprovements over earlier versions and users are strongly advised to upgrade. The installer package will automatically upgrade prior releases. PyObjC is released with an open source license.

1 0

[Application] ISOS/v0.7.1a
by Mehmet Gencer May 4, 2003

May 4, 2003

ISOS/v0.7.1a ------------ A bundle of SMTP, POP3, HTTP servers, and a management console. ISOS is a purely Python server for small organizations. It contains e-mail(SMTP & POP3) servers, a simple HTTP server, and a console based management program for controlling services, creating users and e-mail groups. Most suitable for small organizations that has little expertise in such services and software, and mediocre performance considerations Turkish and English interface. GPL licensed. ISOS provides a quick start for e-presence of small organizations/comapnies, if you don't want to pay for MS Exchange server, and lack the experience to get software like Sendmail, Courier and Apache do what you need. Works on both Windows and Linux. URL: http://isos.acikkanal.net/ Download: http://isos.acikkanal.net/index.en.html License: GPL Platform: Linux, Win32 Categories: Servers Mehmet Gencer (mgencer(a)acikkanal.net) http://isos.acikkanal.net/ -- <a href="http://isos.acikkanal.net/">ISOS/v0.7.1a</a> -- A bundle of SMTP, POP3, HTTP servers, and a management console.

1 0

announce: Epylog-0.9.3
by Konstantin Riabitsev May 3, 2003

May 3, 2003

Epylog Log Analyzer =================== What is it: ----------- Epylog is a new log notifier and parser which runs periodically, looks at your logs, processes some of the entries in order to present them in a more comprehensive format, and then mails you the output. It is written specifically for large network clusters where a lot of machines (around 50 and upwards) log to the same loghost using syslog or syslog-ng. The epylog engine should work on most unix systems running Python-2.2 and above, alhough currently the processing modules are only written to work with linux (and particularly Red Hat Linux series 7 and above). However, other unix and linux flavors should work fine, as long as they use standard non-ancient logging facilities and things like PAM. Features: --------- - Threaded for faster network lookups - Unwraps "last message repeated" lines - Mails reports in either html or plain text (or both) - Publishes reports to a file with optional notification via email. - Accepts --last hour/day/week/month command-line arguments - Handles modules written in both Python and other languages (though many "neat" features are not available to external modules) - External module API fully backwards-compatible with DULog Requirements: -------------- The parsing modules are currently only written for linux, so at least at the moment running it on other unixes would not be very efficient (it will still work as long as syslog is used, but many lines will be unparsed). Requires Python-2.2 or above and PyXML (libxml2-python). Works as-is for Red Hat 7.3, 8.0, and 9 (though see a caution on the site for 9), Yellowdog Linux 3.0. Where to get it: ---------------- http://linux.duke.edu/projects/epylog/ Best regards, -- Konstantin ("Icon") Riabitsev Duke Physics Systems Admin, RHCE www.duke.edu/~icon/pubkey.asc

1 0

PEP 1: PEP Purpose and Guidelines
by David Goodger May 3, 2003

May 3, 2003

I am posting this meta-PEP to inform the Python community of a significant recent addition. Formerly, there was no provision for the BDFL to initiate a PEP review, even if the PEP was sure to be accepted; taken literally, the PEP text required the PEP author to request a review. Such a provision has been added with the following text: For a PEP that is pre-determined to be acceptable (e.g., it is an obvious win as-is and/or its implementation has already been checked in) the BDFL may also initiate a PEP review, first notifying the PEP author(s) and giving them a chance to make revisions. A description of the PEP acceptance criteria was also added immediately following the above text. The processed PEP can be found at <http://www.python.org/peps/pep-0001.html>. ====================================================================== PEP: 1 Title: PEP Purpose and Guidelines Version: $Revision: 1.42 $ Last-Modified: $Date: 2003/05/03 16:01:32 $ Author: Barry A. Warsaw, Jeremy Hylton, David Goodger Status: Active Type: Informational Content-Type: text/x-rst Created: 13-Jun-2000 Post-History: 21-Mar-2001, 29-Jul-2002, 03-May-2003 What is a PEP? ============== PEP stands for Python Enhancement Proposal. A PEP is a design document providing information to the Python community, or describing a new feature for Python. The PEP should provide a concise technical specification of the feature and a rationale for the feature. We intend PEPs to be the primary mechanisms for proposing new features, for collecting community input on an issue, and for documenting the design decisions that have gone into Python. The PEP author is responsible for building consensus within the community and documenting dissenting opinions. Because the PEPs are maintained as text files under CVS control, their revision history is the historical record of the feature proposal [1]_. Kinds of PEPs ============= There are two kinds of PEPs. A Standards Track PEP describes a new feature or implementation for Python. An Informational PEP describes a Python design issue, or provides general guidelines or information to the Python community, but does not propose a new feature. Informational PEPs do not necessarily represent a Python community consensus or recommendation, so users and implementors are free to ignore Informational PEPs or follow their advice. PEP Work Flow ============= The PEP editors assign PEP numbers and change their status. The current PEP editors are David Goodger and Barry Warsaw. Please send all PEP-related email to <peps(a)python.org>. The PEP process begins with a new idea for Python. It is highly recommended that a single PEP contain a single key proposal or new idea. The more focussed the PEP, the more successfully it tends to be. The PEP editor reserves the right to reject PEP proposals if they appear too unfocussed or too broad. If in doubt, split your PEP into several well-focussed ones. Each PEP must have a champion -- someone who writes the PEP using the style and format described below, shepherds the discussions in the appropriate forums, and attempts to build community consensus around the idea. The PEP champion (a.k.a. Author) should first attempt to ascertain whether the idea is PEP-able. Small enhancements or patches often don't need a PEP and can be injected into the Python development work flow with a patch submission to the SourceForge `patch manager`_ or `feature request tracker`_. The PEP champion then emails the PEP editor <peps(a)python.org> with a proposed title and a rough, but fleshed out, draft of the PEP. This draft must be written in PEP style as described below. If the PEP editor approves, he will assign the PEP a number, label it as Standards Track or Informational, give it status "Draft", and create and check-in the initial draft of the PEP. The PEP editor will not unreasonably deny a PEP. Reasons for denying PEP status include duplication of effort, being technically unsound, not providing proper motivation or addressing backwards compatibility, or not in keeping with the Python philosophy. The BDFL (Benevolent Dictator for Life, Guido van Rossum) can be consulted during the approval phase, and is the final arbitrator of the draft's PEP-ability. If a pre-PEP is rejected, the author may elect to take the pre-PEP to the comp.lang.python newsgroup (a.k.a. python-list(a)python.org mailing list) to help flesh it out, gain feedback and consensus from the community at large, and improve the PEP for re-submission. The author of the PEP is then responsible for posting the PEP to the community forums, and marshaling community support for it. As updates are necessary, the PEP author can check in new versions if they have CVS commit permissions, or can email new PEP versions to the PEP editor for committing. Standards Track PEPs consists of two parts, a design document and a reference implementation. The PEP should be reviewed and accepted before a reference implementation is begun, unless a reference implementation will aid people in studying the PEP. Standards Track PEPs must include an implementation -- in the form of code, patch, or URL to same -- before it can be considered Final. PEP authors are responsible for collecting community feedback on a PEP before submitting it for review. A PEP that has not been discussed on python-list(a)python.org and/or python-dev(a)python.org will not be accepted. However, wherever possible, long open-ended discussions on public mailing lists should be avoided. Strategies to keep the discussions efficient include, setting up a separate SIG mailing list for the topic, having the PEP author accept private comments in the early design phases, etc. PEP authors should use their discretion here. Once the authors have completed a PEP, they must inform the PEP editor that it is ready for review. PEPs are reviewed by the BDFL and his chosen consultants, who may accept or reject a PEP or send it back to the author(s) for revision. For a PEP that is pre-determined to be acceptable (e.g., it is an obvious win as-is and/or its implementation has already been checked in) the BDFL may also initiate a PEP review, first notifying the PEP author(s) and giving them a chance to make revisions. For a PEP to be accepted it must meet certain minimum criteria. It must be a clear and complete description of the proposed enhancement. The enhancement must represent a net improvement. The proposed implementation, if applicable, must be solid and must not complicate the interpreter unduly. Finally, a proposed enhancement must be "pythonic" in order to be accepted by the BDFL. (However, "pythonic" is an imprecise term; it may be defined as whatever is acceptable to the BDFL. This logic is intentionally circular.) See PEP 2 [2]_ for standard library module acceptance criteria. Once a PEP has been accepted, the reference implementation must be completed. When the reference implementation is complete and accepted by the BDFL, the status will be changed to "Final". A PEP can also be assigned status "Deferred". The PEP author or editor can assign the PEP this status when no progress is being made on the PEP. Once a PEP is deferred, the PEP editor can re-assign it to draft status. A PEP can also be "Rejected". Perhaps after all is said and done it was not a good idea. It is still important to have a record of this fact. PEPs can also be replaced by a different PEP, rendering the original obsolete. This is intended for Informational PEPs, where version 2 of an API can replace version 1. PEP work flow is as follows:: Draft -> Accepted -> Final -> Replaced ^ +----> Rejected v Deferred Some Informational PEPs may also have a status of "Active" if they are never meant to be completed. E.g. PEP 1 (this PEP). What belongs in a successful PEP? ================================= Each PEP should have the following parts: 1. Preamble -- RFC 822 style headers containing meta-data about the PEP, including the PEP number, a short descriptive title (limited to a maximum of 44 characters), the names, and optionally the contact info for each author, etc. 2. Abstract -- a short (~200 word) description of the technical issue being addressed. 3. Copyright/public domain -- Each PEP must either be explicitly labelled as placed in the public domain (see this PEP as an example) or licensed under the `Open Publication License`_. 4. Specification -- The technical specification should describe the syntax and semantics of any new language feature. The specification should be detailed enough to allow competing, interoperable implementations for any of the current Python platforms (CPython, Jython, Python .NET). 5. Motivation -- The motivation is critical for PEPs that want to change the Python language. It should clearly explain why the existing language specification is inadequate to address the problem that the PEP solves. PEP submissions without sufficient motivation may be rejected outright. 6. Rationale -- The rationale fleshes out the specification by describing what motivated the design and why particular design decisions were made. It should describe alternate designs that were considered and related work, e.g. how the feature is supported in other languages. The rationale should provide evidence of consensus within the community and discuss important objections or concerns raised during discussion. 7. Backwards Compatibility -- All PEPs that introduce backwards incompatibilities must include a section describing these incompatibilities and their severity. The PEP must explain how the author proposes to deal with these incompatibilities. PEP submissions without a sufficient backwards compatibility treatise may be rejected outright. 8. Reference Implementation -- The reference implementation must be completed before any PEP is given status "Final", but it need not be completed before the PEP is accepted. It is better to finish the specification and rationale first and reach consensus on it before writing code. The final implementation must include test code and documentation appropriate for either the Python language reference or the standard library reference. PEP Formats and Templates ========================= There are two PEP formats available to authors: plaintext and reStructuredText_. Plaintext PEPs are written in plain ASCII text, contain minimal structural markup, and should adhere to a rigid style. PEP 9 contains a boilerplate template [3]_ you can use to get started writing your plaintext PEP. ReStructuredText_ PEPs allow for rich markup that is still quite easy to read, but results in much better-looking and more functional HTML. PEP 12 contains a boilerplate template [4]_ for use with reStructuredText PEPs. There is a Python script that converts both styles of PEPs to HTML for viewing on the web [5]_. Parsing and conversion of plaintext PEPs is self-contained within the script. reStructuredText PEPs are parsed and converted by Docutils_ code called from the script. PEP Header Preamble =================== Each PEP must begin with an RFC 822 style header preamble. The headers must appear in the following order. Headers marked with "*" are optional and are described below. All other headers are required. :: PEP: <pep number> Title: <pep title> Version: <cvs version string> Last-Modified: <cvs date string> Author: <list of authors' real names and optionally, email addrs> * Discussions-To: <email address> Status: <Draft | Active | Accepted | Deferred | Rejected | Final | Replaced> Type: <Informational | Standards Track> * Content-Type: <text/plain | text/x-rst> * Requires: <pep numbers> Created: <date created on, in dd-mmm-yyyy format> * Python-Version: <version number> Post-History: <dates of postings to python-list and python-dev> * Replaces: <pep number> * Replaced-By: <pep number> The Author header lists the names, and optionally the email addresses of all the authors/owners of the PEP. The format of the Author header value must be Random J. User <address(a)dom.ain> if the email address is included, and just Random J. User if the address is not given. For historical reasons the format "address(a)dom.ain (Random J. User)" may appear in a PEP, however new PEPs must use the mandated format above, and it is acceptable to change to this format when PEPs are updated. If there are multiple authors, each should be on a separate line following RFC 2822 continuation line conventions. Note that personal email addresses in PEPs will be obscured as a defense against spam harvesters. While a PEP is in private discussions (usually during the initial Draft phase), a Discussions-To header will indicate the mailing list or URL where the PEP is being discussed. No Discussions-To header is necessary if the PEP is being discussed privately with the author, or on the python-list or python-dev email mailing lists. Note that email addresses in the Discussions-To header will not be obscured. The Type header specifies the type of PEP: Informational or Standards Track. The format of a PEP is specified with a Content-Type header. The acceptable values are "text/plain" for plaintext PEPs (see PEP 9 [3]_) and "text/x-rst" for reStructuredText PEPs (see PEP 12 [4]_). Plaintext ("text/plain") is the default if no Content-Type header is present. The Created header records the date that the PEP was assigned a number, while Post-History is used to record the dates of when new versions of the PEP are posted to python-list and/or python-dev. Both headers should be in dd-mmm-yyyy format, e.g. 14-Aug-2001. Standards Track PEPs must have a Python-Version header which indicates the version of Python that the feature will be released with. Informational PEPs do not need a Python-Version header. PEPs may have a Requires header, indicating the PEP numbers that this PEP depends on. PEPs may also have a Replaced-By header indicating that a PEP has been rendered obsolete by a later document; the value is the number of the PEP that replaces the current document. The newer PEP must have a Replaces header containing the number of the PEP that it rendered obsolete. Reporting PEP Bugs, or Submitting PEP Updates ============================================= How you report a bug, or submit a PEP update depends on several factors, such as the maturity of the PEP, the preferences of the PEP author, and the nature of your comments. For the early draft stages of the PEP, it's probably best to send your comments and changes directly to the PEP author. For more mature, or finished PEPs you may want to submit corrections to the SourceForge `bug manager`_ or better yet, the SourceForge `patch manager`_ so that your changes don't get lost. If the PEP author is a SF developer, assign the bug/patch to him, otherwise assign it to the PEP editor. When in doubt about where to send your changes, please check first with the PEP author and/or PEP editor. PEP authors who are also SF committers, can update the PEPs themselves by using "cvs commit" to commit their changes. Remember to also push the formatted PEP text out to the web by doing the following:: % python pep2html.py -i NUM where NUM is the number of the PEP you want to push out. See :: % python pep2html.py --help for details. Transferring PEP Ownership ========================== It occasionally becomes necessary to transfer ownership of PEPs to a new champion. In general, we'd like to retain the original author as a co-author of the transferred PEP, but that's really up to the original author. A good reason to transfer ownership is because the original author no longer has the time or interest in updating it or following through with the PEP process, or has fallen off the face of the 'net (i.e. is unreachable or not responding to email). A bad reason to transfer ownership is because you don't agree with the direction of the PEP. We try to build consensus around a PEP, but if that's not possible, you can always submit a competing PEP. If you are interested in assuming ownership of a PEP, send a message asking to take over, addressed to both the original author and the PEP editor <peps(a)python.org>. If the original author doesn't respond to email in a timely manner, the PEP editor will make a unilateral decision (it's not like such decisions can't be reversed :). References and Footnotes ======================== .. [1] This historical record is available by the normal CVS commands for retrieving older revisions. For those without direct access to the CVS tree, you can browse the current and past PEP revisions via the SourceForge web site at http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/python/python/nondist/peps/ .. [2] PEP 2, Procedure for Adding New Modules, Faassen (http://www.python.org/peps/pep-0002.html) .. [3] PEP 9, Sample Plaintext PEP Template, Warsaw (http://www.python.org/peps/pep-0009.html) .. [4] PEP 12, Sample reStructuredText PEP Template, Goodger, Warsaw (http://www.python.org/peps/pep-0012.html) .. [5] The script referred to here is pep2html.py, which lives in the same directory in the CVS tree as the PEPs themselves. Try ``pep2html.py --help`` for details. The URL for viewing PEPs on the web is http://www.python.org/peps/. .. _patch manager: http://sourceforge.net/tracker/?group_id=5470&atid=305470 .. _feature request tracker: http://sourceforge.net/tracker/?atid=355470&group_id=5470&func=browse .. _Open Publication License: http://www.opencontent.org/openpub/ .. _reStructuredText: http://docutils.sourceforge.net/rst.html .. _Docutils: http://docutils.sourceforge.net/ .. _bug manager: http://sourceforge.net/tracker/?group_id=5470&atid=105470 Copyright ========= This document has been placed in the public domain. -- David Goodger <http://starship.python.net/~goodger> Python Enhancement Proposal (PEP) Editor <http://www.python.org/peps/> (Please cc: all PEP correspondence to <peps(a)python.org>.)

1 0

ANN: numarray-0.5 released
by Todd Miller May 3, 2003

May 3, 2003

Release Notes for numarray-0.5 Numarray is an array processing package designed to efficiently manipulate large multi-dimensional arrays. Numarray is modelled after Numeric and features c-code generated from python template scripts, the capacity to operate directly on arrays in files, and improved type promotions. I. ENHANCEMENTS 1. Universal Function Overhead Reduction The constant time overhead for most universal functions has been reduced by a factor of 10-20. This results in better performance for small arrays. 2. FFT mode and IRAF boundary modes added to Convolve.convolve2d There's now an FFT switch for the 2d convolution function in the Convolve package; when set to 1, convolution is performed via the FFT rather than using the naiive algorithm. In addition, convolve2d now supports boundary modes which are identical to IRAF's convolution function. 3. Numarray is now supported by f2py Numarray numerical arrays can now be used with f2py wrappers for Fortran code. To compile f2py wrapped extensions for numarray, use the switch -DNUMARRAY on the f2py command line. Support is currently restricted to f77 and numerical arrays. II. BUGS FIXED 650926 exotic type coercions 653424 Convolve.boxcar boundary bug 653429 python setup.py build 654669 array index by list 655942 logical operator reductions 657058 inverse real fft bug 677796 byteswap not working 709956 error summing over large boolean arrays 710480 MLab.median makes unnecessary msort call 714537 conjugate function changes its argument See http://sourceforge.net/tracker/?atid=450446&group_id=1369&func=browse for more details. III. CAUTIONS 1. Due to some module renamings, numarray-0.5 will not install correctly on top of an existing numarray installation. Before installing numarray-0.5 remove your old version of numarray. 2. Due to reorganization of the C-API, numarray extensions must be recompiled. 3. For numarray-0.5 and up, the byteswap related methods have been redefined: a.byteswap() swaps but leaves byteorder alone a.togglebyteorder() Does "big" <-> "little" a._byteswap() now an alias for byteswap a._togglebyteorder() deleted 4. round() has been deprecated. Use around() instead. WHERE ----------- Numarray-0.5 windows executable installers, source code, and manual is here: http://sourceforge.net/project/showfiles.php?group_id=1369 Numarray is hosted by Source Forge in the same project which hosts Numeric: http://sourceforge.net/projects/numpy/ The web page for Numarray information is at: http://stsdas.stsci.edu/numarray/index.html Trackers for Numarray Bugs, Feature Requests, Support, and Patches are at the Source Forge project for NumPy at: http://sourceforge.net/tracker/?group_id=1369 REQUIREMENTS ------------------------------ numarray-0.5 requires Python 2.2.2 or greater. AUTHORS, LICENSE ------------------------------ Numarray was written by Perry Greenfield, Rick White, Todd Miller, JC Hsu, Paul Barrett, Phil Hodge at the Space Telescope Science Institute. Thanks go to Jochen Kupper of the University of North Carolina for his work on Numarray and for porting the Numarray manual to TeX format. Thanks also to Edward C. Jones, Francesc Alted, Paul Dubois, Eric Jones, Travis Oliphant, Pearu Peterson and everyone who has contributed with comments and feedback. Numarray is made available under a BSD-style License. See LICENSE.txt in the source distribution for details. -- Todd Miller jmiller(a)stsci.edu

1 0

ANN: apm.py 0.3.0
by Tilo Riemer May 1, 2003

May 1, 2003

Hello, apm.py 0.3.0 is out. DESCRIPTION: apm.py is a python module providing of an uniform and platform independent interface to APM. At the moment it implements only battery relevant functions. WHATS NEW: 1. Support for FreeBSD 4 (tested with FreeBSD 4.8) and OpenBSD (untested) 2. Fix in NetBSD where the charging state could be wrong. HOMEPAGE: http://www.iapp.de/~riemer/projects/apm.py/ Best regards, Tilo

1 0