Mailman 3 December 2002 - Python-announce-list

[Module] NovaGrid 1.0
by Olivier Ravard Dec. 16, 2002

Dec. 16, 2002

NovaGrid 1.0 ------------ A light spreadsheet module written in Python/Tkinter and based on Tktable. Can be packed into larger applications. The NovaGrid spreadsheet is a light spreadsheet entirely written in Python / Tkinter and is a free software under GPL. It is a little module of the NovaRPC project. The NovaGrid spreadsheet (and ploting tool) is hosted by sourforge (http://www.sourceforge.net/projects/novagrid). This spreadsheet features are : - to be light, - it can be " packed " or " placed " in a toplevel or in a frame, - you can inserting and deleting data from a python script, - you can plot data from some or all of data in the spreasheet, - to be multi os (Linux and Windows) URL: http://www.novagrid.com/page.php?p=spreadsheet.html Download: http://www.sourceforge.net/projects/novagrid License: GPL Platform: win32, Linux Requires: Tktable BWidget Gui: Tkinter Categories: Tkinter Widgets Olivier Ravard (olivier.ravard(a)novagrid.com) http://www.novagrid.com -- <a href="http://www.novagrid.com/page.php?p=spreadsheet.html">NovaGrid 1.0</a> -- A light spreadsheet module written in Python/Tkinter and based on Tktable. Can be packed into larger applications.

1 0

EDDIE-Tool 0.31 Released
by Chris Miles Dec. 16, 2002

Dec. 16, 2002

EDDIE-Tool 0.31 has just been released. http://eddie-tool.net/ What is it ? The EDDIE-Tool is an intelligent UNIX monitoring tool written entirely in Python. It provides system, network and security monitoring features, with an extensive configuration facility for defining customized monitoring rules. What is new ? Major new features added are directive dependencies, programmable action call periods, and access to previously collected data within directive rules. Also many more smaller updates such as improved Linux memory and swap usage statistics, more file checks, and support for remote SMTP servers. Why is it interesting to Python users ? Besides system and network administrators, Python users may find EDDIE-Tool interesting as it is an example of a threaded, multi-platform software package, providing easy access to system statistics and using Python's power to offer a dynamic and programmable rules engine. Regards, Chris -- Chris Miles chris(a)psychofx.com http://www.psychofx.com/chris/

1 0

pyPgSQL 2.3 released
by Gerhard Häring Dec. 15, 2002

Dec. 15, 2002

[Yes, I know this announcement is going out a week late] Announce: pyPgSQL - Version 2.3 is released. =========================================================================== pyPgSQL v2.3 has been released. It is available at http://pypgsql.sourceforge.net. pyPgSQL is a package of two (2) modules that provide a Python DB-API 2.0 compliant interface to PostgreSQL databases. The first module, libpq, is written in C and exports the PostgreSQL C API to Python. The second module, PgSQL, provides the DB-API 2.0 compliant interface and support for various PostgreSQL data types, such as INT8, NUMERIC, MONEY, BOOL, ARRAYS, etc. This module is written in Python and works with PostgreSQL 7.0 or later and Python 2.0 or later. It was tested with PostgreSQL 7.0.3, 7.1.3, 7.2.2, 7.3, Python 2.0.1, 2.1.3 and 2.2.2. Note: It is highly recommended that you use PostgreSQL 7.2 or later and Python 2.1 or later. If you want to use PostgreSQL Large Objects under Python 2.2.x, you *must* use Python 2.2.2, because of a bug in earlier 2.2 versions. Project homepages: pyPgSQL: http://pypgsql.sourceforge.net/ PostgreSQL: http://www.postgresql.org/ Python: http://www.python.org/ While there didn't change much under the hood, the build process was completely rewritten, so pyPgSQL should now build out of the box on most popular platforms. For you, this means that a "python setup.py build" will now hopefully just work. And for us, this means we'll have to answer less boring support questions :-) These platforms were tested and will build out of the box (of course, more testing won't hurt): UnixWare 7/OpenUNIX 8, Windows native, Cgwin, FreeBSD 4.7, Redhat Linux 7.3, SuSE Linux 7.3, Debian Linux 3.0. The build process is also designed to work with these platforms, but they could not be tested in real life (please do so, if you can!): Mandrake Linux, NetBSD, OpenBSD, MacOS X. If your platform isn't supported out of the box, you can edit a setup.py file to configure the build process. Patches for supporting additional platforms are more than welcome. Look into setup.py for how to do it. The other big change is that Gerhard finally gave up on getting more feedback on his Unicode patch and merged it into the pyPgSQL 2.x line. Hey, if it did work for Linux 2.4, it can work for us, too <0.7 wink>. Using Unicode works like this: from pyPgSQL import PgSQL con = PgSQL.connect(client_encoding=("utf-8", "ignore"), unicode_results=1) # where client_encoding are the parameters you normally give to the encode # method of a Unicode string. unicode_results=1 means pyPgSQL will return # VARCHAR/CHAR/TEXT fields as Unicode strings instead of byte strings. # As I refuse to do any magic, you'll also have to set the client encoding # for the database manually: cursor = con.cursor() cursor.execute("SET CLIENT_ENCODING TO UNICODE") # There are other ways to set the client encoding, including setting a # special environment variable (see PostgreSQL manual), but I recommend # doing it in code. Support for reference cursors was added. Since PostgreSQL 7.2, you could create cursors in PL/pgSQL and pass a reference to the open cursor back to the client. PgSQL will now cast those referenced cursors into a Cursor object that can be used to fetch the results in the cursor. For example (assuming that mmYearInfo() returns a reference curosr): $ python Python 2.2.2 (#7, Nov 27 2002, 17:10:05) [C] on openunix8 Type "help", "copyright", "credits" or "license" for more information. >>> from pyPgSQL import PgSQL >>> cx = PgSQL.connect(database='esi') >>> cu = cx.cursor() >>> cu.callproc('mmYearInfo') >>> rs = cu.fetchone() >>> rs [<pyPgSQL.PgSQL.Cursor instance at 0x818495c>] >>> c = rs[0] >>> for i in c.description: ... print i ... ['model_year', varchar, 4, 8, None, None, None, 0] ['mktg_div_name', varchar, 50, 54, None, None, None, 0] ['model_desc', varchar, 50, 54, None, None, None, 0] ['book_types', varchar, 50, 54, None, None, None, 0] ['vehicle_syskey', integer, 4, 4, None, None, None, 0] >>> r = c.fetchone() >>> r ['2003', 'Buick', 'Century', '1;8;9', 2211] >>> --------------------------------------------------------------------------- ChangeLog: =========================================================================== Changes since pyPgSQL Version 2.2 ================================= The following source code files were added to Version 2.3 of pyPgSQL: unicode_tests.py - Test suite for the new Unicode support. Merged from the Unicode patch. Changes to setup.py ------------------- * This file was rewritten entirely so that pyPgSQL now builds out of the box on Windows, Cygwin, Debian Linux, Redhat Linux, SuSE Linux, FreeBSD, UnixWare 7 and OpenUNIX 8. These are the platforms the new build process has been tested on. Untested support is available for Mandrake Linux, NetBSD, OpenBSD and MacOS X. Changes to README ----------------- * Updates for 2.3. * Converted the whole document into reStructuredText, so we can easily built a HTML version using docutils (http://docutils.sf.net/). Changes to README.win32 ----------------------- * Remove out of date warning about PostgreSQL on win32 * Reflected change from windows/ to ports/ Changes to PgSQL.py ------------------- * Fixed various problems with the PgNumeric constructor and formatting routines. * Fixed problems with new __setupTransaction function: | 1. Made it a method of Connection, not Cursor. 2. inTransaction was only set if TransactionLevel was set. * Fixed instances where method name was incorrect: Connection__gcCursor -> _Connection__gcCursor Connection__closeCursor -> _Connection__closeCursor * Cleaned up code where there was unneeded references to conn in Connection class. | * Handle the new '__quote__' method for arrays, too. * Still handle '_quote' methods for backwards compatibility. * Fixed changed PG_TIMESTAMP oid, added PG_TIMESTAMPTZ and PG_REFCURSOR oids. * Reference cursors are now type-casted into cursor objects. * Completed the emulation of a String object for the PgBytea and PgOther classes. This corrects several problems with PgBytea concerning compari- sons, using PgBytea types as keys in dictionaries, etc. * Added the __hash__ function to the PgNumeric class. Cleaned up the code in PgNumeric class and made some small improvments to it. * Added the PgArray class. This is a wrapper around a Python list and is used for all PostgreSQL arrays. This change was made so that lists and tuples no longer have a special meaning in the Cursor.execute() method. * Changed the quoting methods defined in the various classes defining PostgreSQL support types to __quote__. * Merged the Unicode patch. pyPgSQL now has full Unicode support. * Added support for the INTERVAL type. * mxDateTime 1.x is no longer supported. Require mxDateTime 2.x and give useful error message if import fails. * Cosmetic changes: use cmp builtin where appropriate. * Fixed typo where PgTypes.__str__ was spelled incorrectly; compare to None using "is" operator. * Take into account that libpq.PgInt8Type might not be available. * Convert ROWID to PgInt8 instead of PgInt4 (the original behaviour led to overflow errors.) * Always set the displaysize field of cursor.description to -1. PostgreSQL 7.3 doesn't provide this information any more and it's pretty useless nowadays that we've mostly left line printers beyond us. Changes to pyPgSQL/__init__.py ------------------------------ * Register libpq.PgInt8 with copy_reg only if available. Changes to pglargeobject.c -------------------------- * Made the 'closed' attribute of PgLargeObject an int instead of a long. Changes to libpqmodule.c: ------------------------- * Fixed the changed PG_TIMESTAMP oid, added PG_TIMESTAMPTZ and PG_REFCURSOR oids. [Bug #845360] * Fixed the format string of ParseTuple in libPQbool_FromInt. This closes a bug that appeared on Linux/Alpha (#625121). Changes to pgversion.c: ----------------------- * Changed pgversion to recognize release canidate versions of PostgreSQL. Changes to PgSQL test cases: ---------------------------- * Updated test cases to allow for changes in PostgreSQL 7.3. * Don't check for the obsolete displaysize field in cursor.description. Also don't check the backend encoding. Multiple files -------------- The windows/ directory has been moved to a port/ directory. Now we *always* use our own version of various string versions instead of special casing for a dozen different Windows and Unix platforms. In order to get the C version of PgInt8Type, it is now required that the constants LLONG_MAX, LLONG_MIN, ULLONG_MAX and ULLONG_MIN are defined when including limits.h and that including Python.h defines HAVE_LONG_LONG. Otherwise, a Python class is used instead.

1 0

Article: "A Python & XML Companion"
by Uche Ogbuji Dec. 15, 2002

Dec. 15, 2002

http://www.xml.com/pub/a/2002/12/11/py-xml.html I offers updates and notes on Python & XML, by Jones and Drake. -- Uche Ogbuji Fourthought, Inc. http://uche.ogbuji.net http://4Suite.org http://fourthought.com Tour of 4Suite - http://www.xml.com/pub/a/2002/10/16/py-xml.html Proper XML Output in Python - http://www.xml.com/pub/a/2002/11/13/py-xml.html RSS for Python - http://www-106.ibm.com/developerworks/webservices/library/ws-p yth11.html Debug XSLT on the fly - http://www-106.ibm.com/developerworks/xml/library/x-deb ugxs.html

1 0

RELEASED: Pymacs 0.21
by pinard＠iro.umontreal.ca Dec. 14, 2002

Dec. 14, 2002

Hello to everybody, and Emacs users in the Python community. A Pymacs flaw has been discovered by Marco Gidde, by which opaque Python references are returned back to Python from Lisp with extra cruft in the communication protocol. I'm even surprised that this problem never hit me yet. I suggest that current Pymacs users upgrade to this new 0.21 version. -------------------- Pymacs is a powerful tool which, once started from Emacs, allows both-way communication between Emacs Lisp and Python. Pymacs aims Python as an extension language for Emacs rather than the other way around, and this assymetry is reflected in some design choices. Within Emacs Lisp code, one may load and use Python modules. Python functions may themselves use Emacs services, and handle Emacs Lisp objects kept in Emacs Lisp space. `http://www.iro.umontreal.ca/~pinard/pymacs/' contains a copy of the Pymacs documentation in HTML form. The canonical Pymacs distribution is available as `http://www.iro.umontreal.ca/~pinard/pymacs/Pymacs.tar.gz'. Report problems and suggestions to `mailto:pinard@iro.umontreal.ca'. -- François Pinard http://www.iro.umontreal.ca/~pinard

1 0

New version of Watch - a typing/mouse monitor
by Skip Montanaro Dec. 14, 2002

Dec. 14, 2002

I'm sick of fiddling with Watch, so I'm announcing a new version. (How's that for arbitrary?) Aside from fixing some annoying bugs and introducing others, the most significant new feature is that it now coordinates activity on multiple systems using a small XML-RPC server to keep track of idle time. Here's a more complete description yanked from the docstring: Watch is a Tk-based program that monitors work and rest times for keyboard and mouse use to help users avoid overuse that can lead to or exacerbate repetitive strain injuries. The user can define the duration of work and rest intervals. In fascist mode, the user can't override the displayed rest window. In friendly mode, a cancel button is available to allow the user to prematurely terminate the rest interval. Watch currently runs on Linux, Windows and MacOSX systems as long as Tkinter is available. It's never been tried on MacOS 9, but there isn't any insurmountable reason why it can't be made to work there either. In case you like the concept, there is still lots to do: * The code's a mess. * The state machine needs to be better separated from Tkinter so that other widget toolkits can be (more easily) substituted for Tkinter. * I believe there's a bug in the transition from the rest phase to the work phase, though I haven't looked closely at that. Until you're happy that it's working reliably, you should enably its friendly mode so you don't get stuck with a cover window that won't disappear. * I don't know how well (or if at all) the XML-RPC server can be spun off from non-Unix platforms. * On non-Linux platforms keyboard activity can either not be tracked or in some situations can only be hinted at (e.g. the jiggle-mouse function for Emacs). * It's completely unpackaged. Originally, it was a single file. It's now three (two applications and a shared module). The only way to get it at the moment is to use CVS. Watch can be found at it's SF home: http://sourceforge.net/projects/watch Feedback is always welcome. -- Skip Montanaro - skip(a)pobox.com http://www.mojam.com/ http://www.musi-cal.com/

1 0

Flightdeck-UI MVM Application + version 0.1.4 released
by fdui＠openlight.com Dec. 13, 2002

Dec. 13, 2002

*** The Flightdeck-UI project is looking for testers and user feedback *** on all platforms. If you come up with your own themes and control *** files, they may be included in the distribution. In addition, *** links to good screenshots can be added to the Flightdeck-UI site. *** The MVM application can also show your name, organization, URL and *** a brief description for any control file or theme that you create. The goal of the Flightdeck-UI project is to apply ideas from aircraft instrumentation design to general purpose user interfaces. This library release 0.1.4 is combined with the Multi-Variable Monitor (MVM) application release 0.1.0. The MVM is a highly configurable Flightdeck-UI application, which includes a graphical editor and theme support. Little (or even none at all) coding is required to use MVM, although everyone is welcome to code as much as they like. Check out the MVM screenshots at "http://www.openlight.com/fdui/screens.html". Linux/Unix users in particular can quickly assemble a monitoring application that would run in a small window on the desktop. An example is included in the distribution. MVM has been tested under Linux (RedHat 7.2) and a little under Windows 95. Although these are still development releases, the MVM should already be a useful application, and will probably look very nice on some corner of your desktop. The project homepage is at "http://www.openlight.com/fdui/". Both the Flightdeck-UI library and the MVM application are open source/free software. They are written in Python and require Tkinter. Questions can be emailed to originating address of this message.

1 0

ANN: Eric 3.0.0 released
by Detlev Offenbach Dec. 13, 2002

Dec. 13, 2002

Hi, after having received no bug reports for the last two weeks I am proud to announce that Eric 3.0.0 is available for download via http://www.die-offenbachs.de/detlev/eric3.html This is the final release. For details see the history file in the distribution. What is it? ----------- Eric 3.0.0 (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 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(a)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(a)die-offenbachs.de

1 0

ANN: Eric 3.0.0 released
by Detlev Offenbach Dec. 13, 2002

Dec. 13, 2002

Hi, After having received no bug reports for the last two weeks I am proud to announce that Eric 3.0.0 is available for download via http://www.die-offenbachs.de/detlev/eric3.html This is the final release. For details see the history file in the distribution. What is it? ----------- Eric 3.0.0 (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 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(a)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(a)die-offenbachs.de

1 0

spyce v1.3.4 released
by Rimon Barr Dec. 13, 2002

Dec. 13, 2002

Spyce v1.3.4 released on 12 Dec 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 Improved explanations of the autosession functionality in the session module based. Changed how request filename is computed under mod_pythod to be slightly more reliable. Fixed Windows installer: it was unable to determine the Python path under certain conditions and bailed. -- Thanks for all the user feedback. Change log v1.3.4 doc updates - session module minor mod_python bug - filename attribute used over environment fix - windows installer unable to find python executable in some cases Enjoy, Rimon.

1 0