Mailman 3 June 2002 - Python-announce-list

Python Cryptography Toolkit 1.9alpha3
by Andrew Kuchling 12 Jun '02

12 Jun '02

This 1.9alpha3 release has a one-line change to 1.9alpha2, fixing a serious ref-counting bug that caused segfaults. My thanks to Piers Lauder and an anonymous user for reporting this problem. A fixed 1.9alpha3 release is available from the PCT's home page: http://www.amk.ca/python/code/crypto.html --amk (www.amk.ca) Time reveals everything. -- The Doctor, in "The Keeper of Traken"

1 0

ANN: leo.py v2.3
by Edward K. Ream 12 Jun '02

12 Jun '02

This is the first announcement of leo.py on comp.lang.python.annouce. leo.py is: 1. An outlining editor. Outlines provide scope for section references. Conversely, extensions to noweb take advantage of outline structure. A single Leo outline can generate multiple derived files. 2. A programmer's editor and a flexible browser for projects, programs, classes or data. Leo supports multiple windows, syntax colorizing for many languages, powerful outline commands, unlimited Undo/Redo and an integrated Python shell(IDLE) window. 3. A project manager. Leo provides multiple views of a project within a single outline. Leo naturally represents tasks that remain up-to-date. People use Leo to manage web sites. 4. A literate programming tool, compatible with noweb and CWEB. Leo features automatic tangling and untangling of derived files. 5. Fully scriptable using Python. 6. Portable. leo.py is a 100% pure Python program. leo.py will work on any platform that supports Python 2.x and the Tk toolkit v8.x. leo.py was developed with Python 2.2 and Tk 8.3.2. 7. Compatible with v2.7 of the Borland/Windows version of Leo. 8. Open Software, distributed under the Python License. 9. Fully supported. Leo's SourceForge site is at: http://sourceforge.net/projects/leo/ You may download all versions of Leo at: http://sourceforge.net/project/showfiles.php?group_id=3458 Leo's CVS site is at: http://sourceforge.net/cvs/?group_id=3458 Edward K. Ream -------------------------------------------------------------------- Edward K. Ream email: edream(a)tds.net Leo: Literate Editor with Outlines Leo: http://personalpages.tds.net/~edream/front.html --------------------------------------------------------------------

1 0

omniORB 3.0.5 / omniORBpy 1.5 released
by Duncan Grisby 12 Jun '02

12 Jun '02

I am pleased to announce the release of omniORB 3.0.5 and omniORBpy 1.5. The releases are minor updates to the previous versions, containing bug fixes and ports to new platforms, but no significant new features. These releases are the first new versions of omniORB since it became an independent project, following the closure of AT&T Laboratories Cambridge. omniORB and omniORBpy are high performance, robust CORBA ORBs for C++ and Python. They are available free under the terms of the GNU LGPL and GPL. You can find more information at http://omniorb.sourceforge.net/ You can download the new versions by following links from that web page, or directly from http://sourceforge.net/project/showfiles.php?group_id=51138 Many thanks to all the people who have contributed to these releases, either by reporting bugs, providing ports to new platforms, or by building binaries. Enjoy! Duncan. -- -- Duncan Grisby -- -- duncan(a)grisby.org -- -- http://www.grisby.org --

1 0

ANNOUNCE: New release of SalStat 20020611
by Alan James Salmoni 12 Jun '02

12 Jun '02

A new release of SalStat, the small friendly statistical analysis package, written in Python and wxPython was made yesterday. The version is 20020611, and is available from the home page at http://salstat.sunsite.dk. Have fun! Alan James Salmoni SalStat.

1 0

ANN: BayPIGgies mailing list *and* meeting
by wesc＠deirdre.org 12 Jun '02

12 Jun '02

in addition to this Wednesday's meeting (see below), the mailing list for BayPIGgies is back up at baypiggies.net please sign up here: http://baypiggies.net/mailman/listinfo/baypiggies if you had given me your e-mail address or business card in the past indicating your interest, you have automagically been added. if, of course, you *don't* want to be on the list, you can also unsubscribe at that same page. you can click on the "View Subscriber List" to see if you have been added yet. here is the main user group website with directions to the meetings and more info: http://deirdre.org/baypiggies thanks, and see some of you Wednesday night @ Stanford! -wesley > From: Wesley J. Chun (wesc(a)deirdre.org) > Subject: BayPIGgies meeting Wed 6/12 7:30pm > Date: 2002-06-10 16:19:35 PST > > What: Python for (Perl) Programmers > Who: Silicon Valley-San Francisco Bay Area Python Users Group (BayPIGgies) > When: Wednesday, June 12, 2002 > Where: Stanford University, Palo Alto, CA > Time: 7:30pm - 9pm > > This is a talk aimed at introducing Python to programmers > familar with Perl and other languages, and serves as a warm-up > to the full tutorial that will be presented at the O'Reilly > Open Source Convention in San Diego near the end of July. > Although the non-Python examples use Perl, it's aimed at > experienced programmers of all sorts. > > Our guest speaker is Aahz, long-time active member of the > Python community. He has been kicking around the computer > industry for more than two decades, doing tech support, > programming, consulting, tech writing, and training. Aahz > recently signed a book contract for an intermediate-level > Python book, which will be published in early 2003. > > More information + directions: http://deirdre.org/baypiggies/ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - "Core Python Programming", Prentice Hall PTR, © 2001 http://starship.python.net/crew/wesc/cpp/ wesley.j.chun :: wesc at deirdre.org cyberweb.consulting : henderson, nv : cyberweb at rocketmail.com http://roadkill.com/~wesc/cyberweb/

1 0

BayPIGgies meeting Wed 6/12 7:30pm
by Wesley J. Chun 10 Jun '02

10 Jun '02

What: Python for (Perl) Programmers Who: Silicon Valley-San Francisco Bay Area Python Users Group (BayPIGgies) When: Wednesday, June 12, 2002 Where: Stanford University, Palo Alto, CA Time: 7:30pm - 9pm This is a talk aimed at introducing Python to programmers familar with Perl and other languages, and serves as a warm-up to the full tutorial that will be presented at the O'Reilly Open Source Convention in San Diego near the end of July. Although the non-Python examples use Perl, it's aimed at experienced programmers of all sorts. Our guest speaker is Aahz, long-time active member of the Python community. He has been kicking around the computer industry for more than two decades, doing tech support, programming, consulting, tech writing, and training. Aahz recently signed a book contract for an intermediate-level Python book, which will be published in early 2003. More information + directions: http://deirdre.org/baypiggies/

1 0

ANNOUNCE: Quixote 0.5
by Greg Ward 10 Jun '02

10 Jun '02

Quixote 0.5 is now available for download from: http://www.mems-exchange.org/software/quixote/ Quixote is yet another framework for developing Web applications in Python. The design goals were: 1) To allow easy development of Web applications where the accent is more on complicated programming logic than complicated templating. 2) To make the templating language as similar to Python as possible, in both syntax and semantics. The aim is to make as many of the skills and structural techniques used in writing regular Python code applicable to Web applications built using Quixote. 3) No magic. When it's not obvious what to do in a certain case, Quixote refuses to guess. If you view a web site as a program, and web pages as subroutines, Quixote just might be the tool for you. If you view a web site as a graphic design showcase, and each web page as an individual work of art, Quixote is probably not what you're looking for. Quixote was primarily written by Andrew Kuchling, Neil Schemenauer, and Greg Ward: {amk,nas,gward}(a)mems-exchange.org. The Quixote documentation is available online: http://www.mems-exchange.org/software/quixote/doc/ Support for Quixote is available on the quixote-users(a)mems-exchange.org mailing list: http://mail.mems-exchange.org/mailman/listinfo/quixote-users CHANGES in Quixote 0.5 ---------------------- * To fix installation problems on Win98 and Mac OS (pre OS X), setup.py now uses os.curdir instead of ''. * Overhauled handling of PublishError exceptions: Quixote now looks for the nearest _q_exception_handler() function in your application's namespace; the format_*error() methods of Publisher are gone. * Documented and overhauled the session management API. If you were previously using session management, you will almost certainly need to change your code; see doc/session-mgmt.txt and doc/session-upgrade.txt. If you've been wanting to use session management in your application but were put off by the lack of documentation, see doc/session-mgmt.txt. Specific changes: * removed the global singleton SessionManager object in session.py and several related functions * removed everything having to do with "application state", an unnecessary abstraction caused by premature over-generalization * removed the 'actual_user' attribute from Session -- it is specific to the MEMS Exchange and just confuses matters in Quixote * made most instance attributes of Session private * defined a sensible persistence API that should work with a wide variety of session persistence schemes * COOKIE_* config variables renamed to SESSION_COOKIE_* * Fix HTTPResponse so that the cookie domain and path can be None, and they will simply not be set in the cookie sent to the client -- that way the browser will simply do the right thing. Set COOKIE_DOMAIN and COOKIE_PATH in config.py to None, since that's usually fine. (You may need to set COOKIE_PATH to "/".) * Subtle but far-reaching change to the publishing algorithm: objects found by the publisher to handle the terminal component of a URL can now be strings as well as callables; a string simply substitutes for a callable's return value. The immediate reason for this was to allow _q_getname() functions to return a string, but a consequence is that you can now put static text in global variables and simply publish them. * Add CHECK_SESSION_ADDR config variable to control whether we check that requests in a session all come from the same IP address, as a defence against playback attacks. (Thanks to Jonathan Corbet.) * In error reports, print the traceback first, ahead of form variables, cookies, and the environment. * Include the HTTP_USER_AGENT variable in access log lines. * Add 'sort' option to SelectWidget class, to force the list of allowed values to be sorted in case-insensitive lexicographic order, with None first. -- Greg Ward - software developer gward(a)mems-exchange.org MEMS Exchange http://www.mems-exchange.org

1 0

Python Cryptography Toolkit 1.9alpha2
by Andrew Kuchling 10 Jun '02

10 Jun '02

I've issued a new release of the Python Cryptography Toolkit, version 1.9alpha2. This version brings back the Crypto.PublicKey and Crypto.Protocol removed from 1.9alpha1, makes a few more backwards-incompatible changes in an attempt to tidy things up, and much of the code has been modernized and tidied up (method renamings, docstrings, test cases, code reformatting, directory rearranging, &c). A full list of changes is below. The Toolkit is a collection of cryptographic algorithms and protocols, implemented for use from Python, and includes the following: Hash functions: MD2, MD4, RIPEMD. Block encryption algorithms: AES, ARC2, Blowfish, CAST, DES, Triple-DES, IDEA, RC5. Stream encryption algorithms: ARC4, simple XOR. Public-key algorithms: RSA, DSA, ElGamal, qNEW. Protocols: All-or-nothing transforms, chaffing/winnowing. Miscellaneous: RFC1751 module for converting 128-key keys into a set of English words, primality testing. The toolkit's home page is: http://www.amk.ca/python/code/crypto.html The code has been tested with Python 2.2, though it will probably work with Python 2.1 as well. Please report bugs via the bug tracker at http://sourceforge.net/projects/pycrypto . There should be at least one more alpha release that will modernize the demos and documentation and add more tests for the random pool module, but I think the incompatible changes are mostly over by this point. (I'm not *sure* of that, which is why this is still an alpha.) --amk (www.amk.ca) Hate world. Hate freeness, it bites! -- Control, in "Ghost Light" 1.9alpha2 ========= * (Backwards incompatible) The old Crypto.Hash.HMAC module is gone, replaced by a copy of hmac.py from Python 2.2's standard library. It will display a warning on interpreter versions older than 2.2. * (Backwards incompatible) Restored the Crypto.Protocol package, and modernized and tidied up the two modules in it, AllOrNothing.py and Chaffing.py, renaming various methods and changing the interface. * (Backwards incompatible) Changed the function names in Crypto.Util.RFC1751. * Restored the Crypto.PublicKey package at user request. I think I'll leave it in the package and warn about it in the documentation. I hope that eventually I can point to someone else's better public-key code, and at that point I may insert warnings and begin the process of deprecating this code. * Fix use of a Python 2.2 C function, replacing it with a 2.1-compatible equivalent. (Bug report and patch by Andrew Eland.) * Fix endianness bugs that caused test case failures on Sparc, PPC, and doubtless other platforms. * Fixed compilation problems on FreeBSD and MacOS X. * Expanded the test suite (requires Sancho, from http://www.mems-exchange.org/software/sancho/) * Added lots of docstrings, so 'pydoc Crypto' now produces helpful output. (Open question: maybe *all* of the documentation should be moved into docstrings?) * Make test.py automatically add the build/* directory to sys.path. * Removed 'inline' declaration from C functions. Some compilers don't support it, and Python's pyconfig.h no longer tells you whether it's supported or not. After this change, some ciphers got slower, but others got faster. * The C-level API has been changed to reduce the amount of memory-to-memory copying. This makes the code neater, but had ambiguous performance effects; again, some ciphers got slower and others became faster. Probably this is due to my compiler optimizing slightly worse or better as a result. * Moved C source implementations into src/ from block/, hash/, and stream/. Having Hash/ and hash/ directories causes problems on case-insensitive filesystems such as Mac OS. * Cleaned up the C code for the extensions.

1 0

[Application] Pyvon
by Fabien HENON 09 Jun '02

09 Jun '02

Pyvon ----- Script editor and raytrace-launcher for POVRAY with Linux POV-RAY editor for Linux with syntax hightlighting, insertions of keywords, starts, stops raytraces, outputs stats and error, displayas line and column numbers, multiples file opening and rendering URL: http://pyvon.sourceforge.net License: GPL Platform: Linux, FreeBsd, Solaris Gui: Tkinter+Pmw Categories: GUI, Application Fabien HENON (fabien.henon(a)caramail.com) http://pyvon.sourceforge.net -- <a href="http://pyvon.sourceforge.net">Pyvon</a> -- Script editor and raytrace-launcher for POVRAY with Linux

1 0

[ANN] constraint-0.2
by Alexandre 07 Jun '02

07 Jun '02

Logilab has released constraint-0.2. The constraint package is an extensible Constraint Satisfaction Problem (CSP) solver using constraint propagation algorithms written in 100% pure Python (tested with Python 2.1) You can download it from ftp://ftp.logilab.org/pub/constraint/, read a bit more about it on http://www.logilab.org/python-logic/constraint.html, and discuss it on the logic-sig mailing list (see http://lists.logilab.org/mailman/listinfo/python-logic to subscribe) The package is still young, but we find it useful enough right now, so I thought I might as well publish it. What can it do? * solve some finite-domain CSP * handle n-ary constraints How can you extend it: * by implementing new Domain classes * by implementing new constraint classes * by implementing new Distributor classes How well does it perform? * 8-queens problems solved in 15 seconds on my 1GHz PC * SEND+MORE=MONEY problem solved in 8 seconds on the same machine What has changed? * a BasicConstraint class was added (these constraint affect only a single variable, and can be entailed in one pass), with several example implementations * The Repository class was refactored, and a Solver class was added as a result, which gives a better separation of the solving logic and storage logic If you're interested by constraint propagation programming in python, please join the logic-sig mailing list. -- Alexandre Fayolle -- LOGILAB, Paris (France). http://www.logilab.com http://www.logilab.fr http://www.logilab.org Narval, the first software agent available as free software (GPL).

1 0