Mailman 3 March 2002 - Python-announce-list

MacPython 2.2.1c1 available
by Jack Jansen March 19, 2002

March 19, 2002

MacPython 2.2.1c1 is available via http://www.cwi.nl/~jack/macpython.html . This is a release candidate for MacPython 2.2.1, expected later this month. Please give it a try and report your findings to pythonmac-sig(a)python.org. This is a patch release, so it should be 100% compatible with MacPython 2.2. This release should run on any MacOS version from 8.1 through 10.1.3 (but for 8.1 you will need to download an additional patch if you want to use the IDE). Many bugs were fixed in this release. The two that deserve special mention are that this release should finally work on a Mac OS X multiprocessor, and that the problems with short read()s from sockets have been addressed. -- - Jack Jansen <Jack.Jansen(a)oratrix.com> http://www.cwi.nl/~jack - - If I can't dance I don't want to be part of your revolution -- Emma Goldman -

1 0

RELEASED: Python 2.2.1c1
by Michael Hudson March 18, 2002

March 18, 2002

We've released a release candidate for the next bugfix release of Python, 2.2.1. Get the scoop (and the files) here: http://www.python.org/2.2.1/ In order to make 2.2.1 a solid release, please help by + Building the release, and running the test suite on your platform. + Building your extension modules and applications against this release, and running *their* test suites. + Reporting any problems to the bug tracker at sf: http://sourceforge.net/bugs/?group_id=5470 This being a bugfix release, there are no exciting new features -- we just fixed a lot of bugs. For a moderately complete list, please see: http://http://sourceforge.net/project/shownotes.php?release_id=80208 Depending on how many problems are found in this release, 2.2.1 final or a second release candidate will follow next week. Extra note for keenies: One of the bugs addressed in this release relates to the behaviour of floating point numbers with respect to under- and over-flow. This has traditionally been an obscure platform-dependent mess. To make sure that this is still the case, I would ask those of you with access to the more unusual platforms (i.e. not Linux/x86, Win32/x86) to run test_math in verbose mode and *email me* the results, including details of platform and OS tested. Thanks. Cheers, The Python development team.

1 0

RELEASED email package version 1.2
by barry＠zope.com March 18, 2002

March 18, 2002

I've released the standalone email package version 1.2. This version has much better support RFC 2047, especially when using multibyte character sets (much thanks go to Ben Gertzfield). A NEWS file excerpt is included below. I will eventually be merging this code into the Python distro, but there are a few new features I want to look at first. One of them includes RFC 2231 support (written by Oleg Broytmann). You can get the standalone email package from SourceForge: http://sourceforge.net/projects/mimelib/ Bug reports to this project please, not to the Python bug tracker (until this code is merged into the Python distro). Enjoy, -Barry -------------------- snip snip -------------------- 1.2 (18-Mar-2002) - In the MIMEText class's constructor, the _encoder argument is deprecated. You will get a DeprecationWarning if you try to use it. This is because there is a fundamental conflict between _encoder and the fact that _charset is passed to the underlying set_payload() method. _encoder really makes no sense any more. - When Message.set_type() is used to set the Content-Type: header, the MIME-Version: header is always set (overriding any existing MIME-Version: header). - More liberal acceptance of parameter formatting, e.g. this is now accepted: Content-Type: multipart/mixed; boundary = "FOO" I.e. spaces around the = sign. - Bug fix in Generator related to splitting long lines in a multiline header. - In class Charset, __str__() method added, as were __eq__() and __ne__(). - Charset.get_body_encoding() may now return a function as well as a string character set name. The function takes a single argument, which is a Message instance, and may change the Content-Transfer-Encoding: header (or do any other manipulations on the message). - Charset.from_splittable() added argument to_output which is used to specify whether the input_codec or the output_codec is used for the conversion (by default, the output codec is used). 1.1 (unreleased) - No changes since 0.97. Only the version number has changed. 0.97 (unreleased) - Message.set_charset() can now take a string naming a character set in addition to a Charset instance. In the former case, a Charset is instantiated by passing the string to its constructor. - The MIMEText constructor now passes the _charset argument to the underlying set_charset() method. This makes things consistent at the cost of a minor semantic change: the resulting instance will have a Content-Transfer-Encoding: header where previously it did not. - A fix for a crash when quopriMIME.encode() tried to encode a multiline string containing a blank line. - New module Header.py which provides a higher level interface for encoded email headers, such as Subject:, From:, and To:. This module provides an abstraction for composing such headers out of charset encoded parts, and for decoding such headers. It properly splits lines on character boundaries even for multibyte character sets. - New RFC compliant base64 and quoted-printable modules, called base64MIME.py and quopriMIME.py. These are intended to replace the Python standard base64.py and quopri.py modules, but are geared toward their use conformant to the various MIME email standards. - The Message class is much more character set aware and RFC compliant: + set_payload() now takes a new optional charset argument + New methods set_charset(), get_charset(), set_param(), del_param(), set_type() + Header parameter quoting is more RFC compliant + get_param() and get_params() now take a new optional unquote argument - The Charset module now knows about utf-8, gb2132, and big5 codecs, the latter two of which are available independently of Python (see the comments in this module for downloading Chinese, Japanese, and Korean codecs). New Charset methods get_body_encoding(), get_output_charset(), encoded_header_len(), header_encode(), and body_encode(). - The Generator now handles encoding the body, if the message object has a character set. - The Utils module has new functions fix_eols() and make_msgid(). It also includes a workaround for bugs in parseaddr() when used with Python versions before 2.2. - A fix for a Parser bug when parsing multipart/* parts that contain only a single subpart.

1 0

PyXMMS and PyXMMS-remote
by Florent Rougon March 17, 2002

March 17, 2002

Hello, WHAT? ----- PyXMMS is a set of Python bindings for all the xmms_remote* functions of the libxmms library, plus some higher-level functions. It can be used to control XMMS (a free multimedia player for X-Window) from a Python program. PyXMMS-remote is an command-line interface to PyXMMS (written in Python). It can be used to do quite a lot of things with an XMMS session from the command-line. EXAMPLES -------- 1) With PyXMMS, you can tell the XMMS session 2 to start playing with import xmms # This is PyXMMS xmms.play(2) With PyXMMS-remote, the same thing is accomplished (from your shell) with the command: pyxmms-remote -s 2 play 2) With PyXMMS, you can write the following call: xmms.enqueue_and_play_launch_if_session_not_started( ("file1.mp3", "file2.ogg", "http://u.r.l.ogg"), "xmms", 0) to: - look if the XMMS session 0 is running and launch XMMS in the background if not (by the way, the two last arguments are optional and could be ommitted here); - add the three audio streams specified to the playlist; - tell the XMMS session 0 to start playing from file1.mp3 With PyXMMS-remote, you can achieve the same thing with: pyxmms-remote E file1.mp3 file2.ogg http://u.r.l.ogg (yes, if you are masochistic, you can also use the not-so-short command name enqueue_and_play_launch_if_session_not_started; you can also specify the session to act on and the XMMS executable name) This command is handy to use with file managers and MIME-aware applications. There are currently 58 commands defined in PyXMMS-remote (as there are about the same number of functions in PyXMMS). DOCUMENTATION -------------- PyXMMS and PyXMMS-remote are well documented. You can browse these documentations on their home page (see below) or (for PyXMMS) using pydoc. LICENSE ------- PyXMMS and PyXMMS-remote are licensed under the GNU GPL. REQUIREMENTS ------------ PyXMMS and PyXMMS-remote have been tested with Python 2.1 and 2.2 and should work on earlier versions with no or very few modifications. HOME PAGE --------- You will find everything about these programs on: <http://www.via.ecp.fr/~flo/index.en.html#PyXMMS_and_PyXMMS-remote> Have fun. -- Florent

1 0

ANN: Python Imaging Library 1.1.3 (march 15, 2002)
by PythonWare March 15, 2002

March 15, 2002

the secret labs proudly presents PIL 1.1.3: The Python Imaging Library (PIL) adds image processing capabilities to your Python interpreter. This library supports many file formats, and provides powerful image processing and graphics capabilities. Version 1.1.3 adds distutils build scripts, improved resampling, screen grabbing support (windows only), and more. Get your copy of the source kit here: http://www.pythonware.com/products/pil/ enjoy, the pil team "Secret Labs -- makers of fine pythonware since 1997."

1 0

Albatross 0.06 released
by Dave Cole March 15, 2002

March 15, 2002

Albatross is a small toolkit for developing highly stateful web applications. The toolkit has been designed to take a lot of the pain out of constructing intranet applications although you can also use Albatross for deploying publicly accessed web applications. In slightly more than 3000 lines of Python you get the following: - An extensible HTML templating system similar to DTML including tags for: - Conditional processing. - Macro definition and expansion. - Sequence iteration and pagination. - Tree browsing. - Lookup tables to translate Python values to arbitrary template text. - Application classes which offer the following features: - Optional server side or browser side sessions. - The ability to place Python code for each page in a dynamically loaded module, or to place all page processing code in a single mainline. - The ability to deploy applications either as CGI or via mod_python by changing less than 10 lines of code. The toolkit application functionality is defined by a collection of fine grained mixin classes. Eight different application types and four different execution contexts are prepackaged, you are able to define your own drop in replacements for any of the mixins to alter any aspect of the toolkit semantics. Application deployment is controlled by your choice of either cgi or mod_python Request class. It should be possible to develop a Request class for FastCGI or Medusa to allow applications to be deployed on those platforms with minimal changes. Albatross comes with over 130 pages of documentation. HTML, PDF and PostScript formatted documentation is available from the toolkit homepage. The toolkit homepage: http://www.object-craft.com.au/projects/albatross/ Important changes since last release: * The template parser has been enhanced to handle attribute values enclosed with either single or double quotes. The enclosing quote character can be used in the attribute string if it is escaped by a backslash ('\'). Attribute values can be broken over multiple lines. * All pickles sent to browser are now MD5 signed to detect and prevent modification. New pickle security techniques can be defined by defining a replacement for the PickleSignMixin class. * The new RandomPageModuleMixin class now allows you to build applications which use the request URL to determine which page module will be used to process the browser request. * A set of classes for implementing file based server side sessions has been added. * The simple session server can now be run as a daemon under Unix. * Program mainline for mod_python deployment has been simplified. You now hook into mod_python like this: def handler(req): return app.run(Request(req)) instead of this: from mod_python import apache : def handler(req): app.run(Request(req)) return apache.OK * New redirect() execution context method for doing browser redirection. * Session saving can be disabled via the new set_save_session() method. * The samples have been completely reorganised and documentation updated to make them less confusing. An installation program has been provided to reduce the pain of running the samples. * Many documentation improvements. - Dave -- http://www.object-craft.com.au

1 0

ANN: Logging Module for Python conforming to PEP 282, first release
by vinay_sajip＠yahoo.co.uk March 15, 2002

March 15, 2002

I've just made available the first release of a logging module for Python. It broadly conforms to PEP 282(see http://python.sourceforge.net/peps/pep-0282.html - though that is still a work in progress). The distribution contains simple examples such as logging to console, file and streaming sockets. The simplest example might be # -- app.py --------------------- import logging logging.info("Starting...") logging.warn("Nothing to do!") logging.info("Done...") # -- end ------------------------ and logging levels DEBUG, INFO, WARN, ERROR, and FATAL are supported. Handling of exception information (tracebacks) is supported. Plus a whole lot more! Levels, Loggers, Handlers, Formatters, Filters... The documentation can be found at http://www.red-dove.com/python_logging.html Development status is pre-alpha but it has been tried out (I won't say "tested" :-)) on 1.5.2 and 2.1.1, Windows platforms. I'm dying to get feedback so please try it out! You can email me via the link on the documentation page, or give feedback via comp.lang.py if you deem it appropriate. Thanks & Regards Vinay Sajip Red Dove Consultants Ltd.

1 0

ANN: PythonCard 0.6.4
by Kevin Altis March 14, 2002

March 14, 2002

This release includes walkthroughs to get you started with PythonCard, an improved layout editor (resourceEditor sample), and new samples that use SOAP and XML-RPC (Blogger API). All the information you need about PythonCard can be found on the project web page at: http://pythoncard.sourceforge.net/ You can download the latest release at: http://sourceforge.net/project/showfiles.php?group_id=19015 For a list of the samples that have been built with PythonCard and some screenshots of them in action go to: http://pythoncard.sourceforge.net/samples.html A description of each sample is included in the readme.txt file in each sample directory. The kind people at SourceForge host the project: http://sourceforge.net/projects/pythoncard/ If you want to get involved the main contact point is the Mailing list: http://lists.sourceforge.net/lists/listinfo/pythoncard-users PythonCard requires Python 2.1.x or later and wxPython 2.3.2.1 or later and runs on every platform those are available for. wxPython can be downloaded at http://www.wxpython.org/ ka --- Kevin Altis altis(a)semi-retired.com

1 0

Next version of PEP278 - universal newline support - available
by Jack Jansen March 13, 2002

March 13, 2002

Folks, the next version of PEP278, universal newline support, and the accompanying patch are available for your review and testing. The patch has changed very little: - open(filename, 'U') is now the way to open files for universal newline reading because 't' may have a use on Windows; - --with-universal-newlines is now the default configure option. The PEP has changed a bit more, mainly addressing issues brought up by Guido and Greg Ward. Please read, test and comment, -- - Jack Jansen <Jack.Jansen(a)oratrix.com> http://www.cwi.nl/~jack - - If I can't dance I don't want to be part of your revolution -- Emma Goldman -

1 0

tarfile 0.2.5
by Lars Gust�bel March 13, 2002

March 13, 2002

tarfile 0.2.5 tarfile is a pure python module that allows read and write access to tar and tar.gz archives. Its interface is compatible to the zipfile standard module. This will make it easy to integrate it in existing projects that already use zipfile, for example. some other features: - platform independent - handles all common file types: files, directories, symlinks and fifos - manages GNUtar extensions like longnames and longlinks - stores all meta-information about files, like permission, modification time, username, user id etc. - rather fast It is available at: http://www.gustaebel.de/lars/tarfile/ I hope, it will be useful. Suggestions, comments and patches are welcome. Lars Gustaebel (lars(a)gustaebel.de)

1 0