Mailman 3 June 2004 - Python-announce-list

process.py: updated popen5 module
by Peter Åstrand June 19, 2004

June 19, 2004

Seven months ago, I announced my popen5 module. Since then, I've made many changes: * The module has been renamed, and is now called 'process'. (As a separate project, this is bad name since there are already several other modules called 'process', but one explicit goal of this module is to have it included in the Python standard library. In this context, 'process' is the best suggestion so far.) * Support for Windows platforms has been added. Currently, the win32all extensions are required. (The idea is to remove this dependency by writing a small extension module, in the same way as _winreg works. Help is always appreciated...) * The run() function has been replaced with call() and callv(). See the documentation for details. * The attributes fromchild, tochild, and childerr has been renamed to stdout, stdin and stderr. * Many small improvements has been made, both in the module itself and the module tests. Note: The PEP is not yet updated to reflect these changes. The license is Python-style. The latest revision is 1.2, and is available from http://www.lysator.liu.se/~astrand/popen5/ . /Peter Astrand <astrand(a)lysator.liu.se> <P><A HREF="http://www.lysator.liu.se/~astrand/popen5/">process.py revision 1.2</A> - updated popen5 module (2004-06-04)

1 0

RELEASED: pynits 040617
by François Pinard June 17, 2004

June 17, 2004

Hi, my Python and Vim friends. Here is the second release of `pynits'. The documentation has been revised. Messages have been internationalised, defaulting to English, with French as a localisation. Thanks to those who were courageous enough to look at the initial release! :-) ============================================================================== Pynits is a useful tool while editing Python source code from within Vim, for tidying up individual sources lines, and doing some auxiliary tasks. I find it particularly helpful when formatting lines containing long or complex expressions. This tool requires a Python-enabled Vim. The Pynits tool may be downloaded from: http://fp-etc.progiciels-bpi.ca/showfile.html?mode=archives while installation directions may be found at: http://fp-etc.progiciels-bpi.ca/showfile.html?name=pynits/README The documentation file is also available on the Web as: http://fp-etc.progiciels-bpi.ca/showfile.html?name=pynits/pynits.txt There are three sets of commands in this tool. A first set takes an entire line of Python source code (which may contain line continuations) and works hard at choosing a "best" surface representation, completely rebuilt from its syntax tree. A second set is meant to discover and report various formatting nits, and even to correct them when a correction recipe is known. A final set contains random commands, usually for a few simple reformatting tasks. -- François Pinard http://www.iro.umontreal.ca/~pinard

1 0

python-dev Summary for 2004-05-01 through 2004-05-31
by Brett June 17, 2004

June 17, 2004

python-dev Summary for 2004-05-01 through 2004-05-31 ++++++++++++++++++++++++++++++++++++++++++++++++++++ This is a summary of traffic on the `python-dev mailing list`_ from May 01, 2004 through May 31, 2004. It is intended to inform the wider Python community of on-going developments on the list. To comment on anything mentioned here, just post to `comp.lang.python`_ (or email python-list(a)python.org which is a gateway to the newsgroup) 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 forty-first and forty-second summaries written by Brett Cannon (out of school and employed for the summer). To contact me, please send email to brett at python.org ; I do not have the time to keep up on comp.lang.python and thus do not always catch follow-ups posted there. All summaries are archived at http://www.python.org/dev/summary/ . Please note that this summary is written using reStructuredText_ which can be found at http://docutils.sf.net/rst.html . Any unfamiliar punctuation is probably markup for reST_ (otherwise it is probably regular expression syntax or a typo =); you can safely ignore it, although I suggest learning reST; it's simple and is accepted for `PEP markup`_ and gives some perks for the HTML output. 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`_. .. _PEP Markup: http://www.python.org/peps/pep-0012.html The in-development version of the documentation for Python can be found at http://www.python.org/dev/doc/devel/ and should be used when looking up any documentation on new code; otherwise use the current documentation as found at http://docs.python.org/ . PEPs (Python Enhancement Proposals) are located at http://www.python.org/peps/ . To view files in the Python CVS online, go to http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/python/ . Reported bugs and suggested patches can be found at the SourceForge_ project page. The `Python Software Foundation`_ is the non-profit organization that holds the intellectual property for Python. It also tries to forward the development and use of Python. But the PSF_ cannot do this without donations. You can make a donation at http://python.org/psf/donations.html . Every penny helps so even a small donation (you can donate through PayPal or by check) helps. .. _python-dev: http://www.python.org/dev/ .. _SourceForge: http://sourceforge.net/tracker/?group_id=5470 .. _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 .. _PSF: .. _Python Software Foundation: http://python.org/psf/ .. contents:: .. _last summary: http://www.python.org/dev/summary/2004-05-01_2004-05-31.html .. _original text file: http://www.python.org/dev/summary/2004-05-01_2004-05-31.ht Summary Announcements ===================== The Spring quarter is now finished for me, so hopefully over the summer I can go back to a semi-monthly schedule (work permitting). 2.3.4 was released during the coverage time of this summary. Everyone should upgrade if possible to this bugfix release. 2.4a should be ready by mid-July. The email server I use (not under my control) decided to change their IMAP server. Unfortunately it is not playing nicely with Thunderbird or the mbox format, so I am being forced to use Apple Mail in order to delete emails. Since I am not used to Mail's threading I may have missed some threads. If I did, sorry about that and they will be covered in the next summary. Summaries ========= ----------------------------- Generator expressions are in! ----------------------------- Generator expressions have been checked in. They are currently using late bindings (see the `last summary`_ for an explanation of what that means). If using late binding semantics doesn't work for you, do express your opinion since it can be changed before the beta is released. Contributing threads: - `PEP 289 - Generator Expressions <http://mail.python.org/pipermail/python-dev/2004-May/044684.html>`__ - `PEP 289 - Generator Expressions - Let's Move For ward <http://mail.python.org/pipermail/python-dev/2004-May/044643.html>`__ ------------------------------------------ Following the docs, not the implementation ------------------------------------------ What happens if you rely on an implementation when the documentation explicitly states the semantics in another way? Well, "you will pay for your sin in a special kind of hell set aside for people who take the implementation as the spec" according to Guido. Some things in CPython go against the spec for performance reasons, but there is nothing stopping from it being changed at another point to more closely follow the spec. Contributing threads: - `Passing compile(...,'exec') code to 'eval' <http://mail.python.org/pipermail/python-dev/2004-May/044683.html>`__ --------------------------------------------- What you need to get a module into the stdlib --------------------------------------------- In order to prevent the stdlib from getting bloated with unneeded modules, new ones need to have seen use "in the field", as Guido put it. Contributing threads: - `New Subscriber <http://mail.python.org/pipermail/python-dev/2004-May/044709.html>`__ --------------------- 2.3.4 is out the door --------------------- Python 2.3.4 has been released. Being a bugfix there are no new features. It is recommended that everyone upgrade to this version. Contributing threads: - `Python 2.3.4 schedule <http://mail.python.org/pipermail/python-dev/2004-May/044661.html>`__ - `release23-maint tree closed for 2.3.4rc1 <http://mail.python.org/pipermail/python-dev/2004-May/044771.html>`__ - `Python 2.3.4, release candidate 1 - BUG FIX <http://mail.python.org/pipermail/python-dev/2004-May/044854.html>`__ - `python 2.3.4 delayed for a week <http://mail.python.org/pipermail/python-dev/2004-May/044921.html>`__ - `2.3.4 release this thursday <http://mail.python.org/pipermail/python-dev/2004-May/044954.html>`__ - `ELEASED Python 2.3.4 (final) <http://mail.python.org/pipermail/python-dev/2004-May/044984.html>`__ ----------------------- IPv6 for Windows in 2.4 ----------------------- For those of you wanting IPv6 support on Windows in the binary build, you will get it in 2.4 . The reason it isn't in 2.3.x is that the branch is compiled with VC 6 which can only compile in IPv6 support with a separate SDK. VC 7, on the other hand, does not have this issue. Contributing threads: - `IPv6 support in Win binary again <http://mail.python.org/pipermail/python-dev/2004-May/044779.html>`__ ----------------------- cookielib in the stdlib ----------------------- A module named cookielib was added to the stdlib to allow transparent handling of cookies for modules such as urllib2. Contributing threads: - `cookielib module in 2.4? <http://mail.python.org/pipermail/python-dev/2004-May/044785.html>`__ - `cookielib <http://mail.python.org/pipermail/python-dev/2004-May/045015.html>`__ ------------------------ cmp doesn't call __cmp__ ------------------------ It was pointed out that calling ``cmp(x,x)``` does not call ``x.__cmp__(x)`` but instead uses PyObject_RichCompareBool(). The issue with this is that PyObject_RichCompareBool() has a short-circuit for when the object being compared is the same, thus skipping a possible call to x.__cmp__ and saving some time. This can be an issue, though, if you want something other than True or False to be returned. Basically what came out of this thread was that C functions can short-circuit comparisons so be careful if you want to make sure that __cmp__ is called; use '==' and the other comparison operators instead. Contributing threads: - `cmp(x,x) <http://mail.python.org/pipermail/python-dev/2004-May/044885.html>`__ ---------------------------------- Posssible improvements to import.c ---------------------------------- Tim Peters asked if anyone knew the working details of import.c; no one spoke up. The question was brought up because Tim would like to see failed imports not lead to mangled modules being in sys.modules and thus being considered properly imported. The suggestion of also handling circular imports came up as well. Contributing threads: - `import.c <http://mail.python.org/pipermail/python-dev/2004-May/044998.html>`__

1 0

ANN: ElementTree 1.2 release candidate 1
by Fredrik Lundh June 16, 2004

June 16, 2004

The Element type is a simple but flexible container object, designed to store hierarchical data structures, such as simplified XML infosets, in memory. The ElementTree package provides a Python implementation of this type, plus code to serialize element trees to and from XML files. The 1.2 release adds limited support for XPath and XInclude, and also fixes a number of serialization bugs, mostly related to extensive use of namespaces and unicode in tags and attribute names. For a complete list of changes, see the CHANGES document in the source kit. You can get the ElementTree toolkit from: http://effbot.org/downloads Brief documentation and some code samples (including an XML-RPC unmarshaller in 16 lines) are available from: http://effbot.org/zone/element.htm enjoy /F

1 0

[ANNOUNCE] Sixteenth release of PythonCAD now available
by Art Haas June 16, 2004

June 16, 2004

Hi. Due to packaging problems in the fifteenth release, and a code snafu the bit the Cocoa interface, I'm releasing the sixteenth version of PythonCAD. The missing Cocoa files have been added, and a patch addressing the Layer problems on Cocoa have been applied. Additionally a small patch for chamfers and fillets is in this release as well, but otherwise this release is identical to the fifteenth release. My thanks to David Haas for contributing the Cocoa interface code, and resolving the problems in the fifteenth release. Art Haas -- Man once surrendering his reason, has no remaining guard against absurdities the most monstrous, and like a ship without rudder, is the sport of every wind. -Thomas Jefferson to James Smith, 1822

1 0

ANN: Spineless game engine 0.0.1
by Jussi Lepistö June 16, 2004

June 16, 2004

Spineless is a generic 3D game engine implemented in Python with C++ optimizations. Focus is on clean design and ease of use, not pure speed. It is still very incomplete and not really useful yet for serious use, but I would appreciate feedback, comments and suggestions. Notable features: - Clean design - Both 2D and 3D graphics accelerated with OpenGL - Custom, completely resolution-independent GUI module - Resource management (fonts, textures, sound samples) - Scene graph with collision detection - Physical simulation with collision response and friction Note that the engine is still very unpolished and unoptimized and lacks proper documentation. However, you can mail me with questions and suggestions. You can find the Spineless web page here: http://spineless.sourceforge.net/ -Jussi

1 0

ANN: IbPy 0.4 - Interactive Brokers Python API
by Troy Melhase June 15, 2004

June 15, 2004

IbPy - Interactive Brokers Python API ===================================== IbPy 0.4 Released 15 June 2004 What is IbPy? ------------------------------------------------------------------------------ IbPy is a third-party implementation of the API used for accessing the Interactive Brokers on-line trading system. IbPy implements functionality that the Python programmer can use to connect to IB, request stock ticker data, submit orders for stocks and futures, and more. What's new in this release? ------------------------------------------------------------------------------ The focus of this release is compatibility with recent versions of the TWS application. TWS Build 826.4 is the most current as of this writing, and IbPy functions as expected with it. The other notable features of this release are: * Execution filters * Orders with combo legs * Method 'request_auto_open_orders' * Method 'request_all_open_orders' * Method 'request_managed_accounts' Many thanks to Mike Lynch for his testing and feedback. Where can I get IbPy? ------------------------------------------------------------------------------ IbPy is available for download from SourceForge.net. http://sourceforge.net/project/showfiles.php?group_id=53862 Project page: http://ibpy.sourceforge.net/ How do I use IbPy? ------------------------------------------------------------------------------ In order to use IbPy, the TWS application provided by IB must be installed and running. See the note "What is TWS?" for more information. IbPy is used in the same manner as all socket clients supplied by Interactive Brokers. The typical sequence of operations is: * Start the browser-based or stand-alone TWS application * In TWS, enable socket clients via the Configure -> API menu * Connect to TWS from external application * In TWS, accept the incoming connection * External application requests ticker updates, sends orders, receives account data, portfolio data, etc. To connect to TWS and interact with the brokers trading system, the Python developer defines methods or functions to act as callbacks and associates these with an Ib.Socket.SocketConnection object. Refer to the Demo.py file in the distribution for a complete example. In lieu of IbPy documentation, developers are referred to the IbPy source code and the documentation supplied by Interactive Brokers. What are the requirements? ------------------------------------------------------------------------------ IbPy requires Python 2.3 or newer. Previous versions may or may not work. TWS requires a web browser capable of executing Sun(R) Java(tm) applets. TWS can also be started directly with Sun(R) Java(tm) and the stand-alone package supplied by Interactive Brokers. What is Interactive Brokers? ------------------------------------------------------------------------------ >From the "About The Interactive Brokers Group" page (http://interactivebrokers.com/html/companyInfo/about.html): The Interactive Brokers Group is a group of electronic brokerage and market making firms at the forefront of the electronic brokerage industry. We have revolutionized the securities and derivatives markets by providing investors with high-speed, direct access to stock, options and futures products worldwide. We specialize in providing investors with technology that offers efficient, fast access to the world's markets at the lowest possible cost. What is TWS? ------------------------------------------------------------------------------ >From the page "Trader Execution and Clearing System Features" (http://interactivebrokers.com/html/companyInfo/market_ib.html): * IB's Trader Workstation can be run directly from your browser, or you can install it on your PC and run it from your desktop. This Java based application allows traders to quickly enter orders and see results. * Direct Access: Unlike other "online" brokers that send your order through an e-mail type system, IB offers a direct-access order entry system that transmits your order to the proper market center, usually within one second of entry. * Real-Time Streaming Quotes: Display real-time, streaming quotes for markets of interest to the investor. Quotes are live and change continuously as the markets change, no periodic manual update or "refresh" is required. What Else? ------------------------------------------------------------------------------ IbPy is not a product of Interactive Brokers, nor am I affiliated with IB. I am a satisfied IB customer, of course. IbPy is installed with distutils. Refer to the Python distutils documentation for more information. The digest version is: # tar xzf IbPy-0.4.tar.gz # cd IbPy-0.4 # python setup.py install The TWS demo system is available here: http://interactivebrokers.com/cgi-pub/jtslink.pl?user_name=edemo The stand-alone TWS and other API software is available from IB: http://interactivebrokers.com/ IbPy is licensed under the BSD License. I'm very interested in your experience with IbPy. Please drop me an note with any feedback you have. Troy Melhase mailto:troy@gci.net

1 0

ANNOUNCE: Quixote 1.0c1 released
by Neil Schemenauer June 15, 2004

June 15, 2004

Quixote is yet another framework for developing Web applications in Python. Version 1.0c1 of Quixote is now available. Note that is the first release candidate for version 1.0. For the list of changes and to download, please see: http://www.mems-exchange.org/software/quixote/

1 0

[ANNOUNCE] Fifteenth release of PythonCAD now available
by Art Haas June 15, 2004

June 15, 2004

I'm pleased to announce the fifteenth development 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 or Python 2.3. 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 fifteenth release of PythonCAD offers users on Mac OS X a native, Cocoa based interface utilizing the Python/Objective-C bridge. The Python/Objective-C code is available at http://pyobjc.sf.net/. A nice side benefit from the development of the Cocoa code was the exposure of various bugs and design issues in the interface neutral code. Bugs exposed by this work have been fixed, and several design improvements are now in the code thanks to this work. The Cocoa interface code is contributed by David Haas, and I thank him greatly for his work. This release includes several more undo/redo improvements. The addition and removal of points on a polyline can now be undone or redone, and assorted other editing operations have improved undo/redo handling as well. A variety of bug fixes have also been added in this release. Small bugs regarding entity searching, arc boundaries, layer addition and removal, and entity storage have been fixed. A few code improvements appear in this release also. The mailing list for the development and use of PythonCAD is available. Visit the following page for information about subscribing and viewing the mailing list archive: http://mail.python.org/mailman/listinfo/pythoncad 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 -- Man once surrendering his reason, has no remaining guard against absurdities the most monstrous, and like a ship without rudder, is the sport of every wind. -Thomas Jefferson to James Smith, 1822

1 0

Alpha 2.3.3 port to Symbian OS UIQ (P800, P900) available
by Tim Ocock June 15, 2004

June 15, 2004

At http://www.monkeyhouse.eclipse.co.uk/mobile/python.htm you can find my independent attempt to port Python to Symbian OS devices. It is a new port from the generic Python 2.3.3 sources. The Python interpreter works in console mode, and most of the standard library modules work as expected. I am launching the project publicly now as I have completed the first proof of concept and am now inviting ideas and contributions. There is still lots of work to do. The software runs inside the emulator, but is of no use on a real device as there is no way to enter text (except possibly with an IR keyboard, but I haven't tried that). I have not seen the Nokia Series 60 runtime, but am aware of it. I don't know what their intentions are regarding open source licensing, but if their work is available on appropriate terms, then I would rather use that for this project than reinvent the wheel. Currently, the Python interpreter runs and you can interactively enter Python programs or code fragments. Please get in touch if you are interested in contributing.

1 0