Mailman 3 March 2003 - Python-announce-list

Call for Participation: EuroPython 2003
by europython＠python.org March 19, 2003

March 19, 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 Monday, April 21. You can propose a 30 minute talk, a 45 minute talk, or a 2 hour tutorial. To propose a talk or tutorial, please visit the Talk Submission page at <http://www.europython.org/Talks/callFor>. 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/>. Also, if you would like to help us make this year's EuroPython conference another success, please volunteer! You can join us on the EuroPython mailing list at <http://mail.python.org/mailman/listinfo/europython>. 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 <info(a)europython.org>.

1 0

python-dev Summary for 2003-03-01 through 2003-03-15
by drifty＠bigfoot.com March 19, 2003

March 19, 2003

+++++++++++++++++++++++++++++++++++++++++++++++++++++ python-dev Summary for 2003-03-01 through 2003-03-15 +++++++++++++++++++++++++++++++++++++++++++++++++++++ This is a summary of traffic on the `python-dev mailing list`_ from March 1, 2003 through March 15, 2003. It is intended to inform the wider Python community of on-going developments on the list and to have an archived summary of each thread started on the list. To comment on anything mentioned here, just post to python-list(a)python.org or `comp.lang.python`_ 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 thirteenth summary written by Brett Cannon (same number as my predecessor, Michael Hudson =). 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_ (else it is probably regular expression syntax); you can safely ignore it (although I suggest learning reST; its simple and is accepted for PEP markup). 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. .. _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 .. _last summary: http://www.python.org/dev/summary/2003-02-16_2003-02-28.html .. contents:: ====================== Summary Announcements ====================== As I am sure most readers of this summary know by now, I am going to PyCon_. This means that I will be occupied the whole last week of this month. I suspect python-dev traffic will be light since I believe most of PythonLabs will be at Pycon and thus not working. =) But still, I will be occupied myself and thus won't have a chance to work on the summary until I come home. This means you should expect the next summary to be rather late. I will get to it, though, at some point. And in case you haven't yet, register for PyCon_. .. _PyCon: http://www.python.org/pycon/ =============================== `Ridiculously minor tweaks?`__ =============================== __ http://mail.python.org/pipermail/python-dev/2003-March/033962.html Splinter threads: - `How long is your shopping tuple? <http://mail.python.org/pipermail/python-dev/2003-March/033996.html>`__ - `Tuples vs lists <http://mail.python.org/pipermail/python-dev/2003-March/033981.html>`__ - `Re: lists v. tuples <http://mail.python.org/pipermail/python-dev/2003-March/034029.html>`__ - `mutability <http://mail.python.org/pipermail/python-dev/2003-March/034057.html>`__ The original point of this thread was Jeremy Fincher finding out if patches changing lists to tuples where the list was not mutated would be accepted for a miniscule performance boost (the answer was no). But this wasn't the interesting knowledge that came out of this thread. This thread led to Guido stating his intended uses of tuples and lists. And you might be going, "lists are for mutable sequences of objects while tuples are for immutable sequences of objects". Well, that is not what Guido thinks of lists and tuples (and don't feel bad if you thought otherwise; Christian Tismer didn't even know what Guido had in mind and Python does not exactly require you to agree with Guido on this). Turns out that tuples, in Guido's view of the world, are "for heterogeneous data" and "list[s] are for homogeneous data"; "Tuples are *not* read-only lists". Guido spelled out his thinking on this in a later email. He basically said that he viewed lists as "a sequence of items of type X" while tuples are more like "a sequence of length N with items of type X1, X2, X3, ..." This makes sense since lists can be sorted while tuples can't; sorting on different types don't necessarily result in a sequence sorted the way you think about it. And if you are still having issues of wrapping your head around this, just view tuples as structs and lists as arrays as in C. This thread then led to another topic of comparisons_ in Python. Guido ended up mentioning how he wished == and != worked on all types (with disparate types always being !=) while all of the other comparisons only worked on similar types for the interpreter's default comparison abilities. This then led to Guido saying how he wished the __cmp__() magic method and the cmp() built-in didn't exist. This is because there are currently two ways to do comparisons; __cmp__(), and then all of the other rich comparison magic methods. You can implement the same functionality as __cmp__() using just __lt__() and __eq__(). There can also be an unneeded performance penalty for __cmp__() since (using the previously mentioned way of re-implementing __cmp__()) you might have to do some unneeded comparisons when all you need is __eq__(). This discussion is still going on. .. _comparisons: http://www.python.org/dev/doc/devel/ref/customization.html#l2h-91 =========================== `Capabilities in Python`__ =========================== __ http://mail.python.org/pipermail/python-dev/2003-March/033820.html Splinter threads: - `Capabilities <http://mail.python.org/pipermail/python-dev/2003-March/033854.html>`__ - `about candy <http://mail.python.org/pipermail/python-dev/2003-March/033986.html>`__ This is a continuation of a discussion covered in the `last summary`_. This was *definitely* the thread from hell for this summary. =) It is very long and there was confusion at multiple points over terminology. You have been warned. Three things were constantly being discussed in this thread; restricted execution, capabilities, and proxies. We discuss them in this order. Restricted execution basically cuts out access to certain objects at execution time. Currently, if you replace the global __builtins__ with something other then what __builtin__.__dict__ has then you enable restricted execution in Python. This cuts off access to built-in objects so as to prevent you from circumventing security code by, for instance, importing the sys_ module so you can replace a module's code in sys.modules. Both capabilities and proxies are worthless without restricted execution since they could be circumvented without it. Capabilities can be viewed as references or bound methods (but not both at the same time, necessarily). Security with capabilities is done based on possession; if you hold a reference to an object you can use that object without issue. The distribution of capabilities becomes the issue with this system. Proxies are a wrapper around objects that restrict access to the object. This restriction extends all the way to the core; even core code such as built-ins can't get access to parts of a proxied object that it doesn't want any object to get a hold of. The trick with proxies is making them secure on their own since they get passed around without worrying who gets it since it is the proxy that provides security, not possession like with capabilities. Two examples of proxies are `Zope proxies`_ and mxProxy_. There was talk of a PEP on all of this but one has not appeared yet; it is currently being worked on by Ben Laurie, though. .. _sys: http://www.python.org/dev/doc/devel/lib/module-sys.html .. _Zope proxies: http://dev.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/Transition… .. _mxProxy: http://www.egenix.com/files/python/mxProxy.html ========= Quickies ========= `Codec registry <http://mail.python.org/pipermail/python-dev/2003-March/033805.html>`__ Gustavo Niemeyer asked someone to review a patch. `Changes to logging in CVS <http://mail.python.org/pipermail/python-dev/2003-March/033811.html>`__ Vinay Sajip if someone checked-in changes to the logging_ package could be rolled back since it broke compatibility with Python 1.5.2 which the logging package tries to keep (as mentioned in `PEP 291`_). The changes were removed. .. _logging: http://www.python.org/dev/doc/devel/lib/module-logging.html .. _PEP 291: http://www.python.org/peps/pep-0291.html `__slots__ for metatypes <http://mail.python.org/pipermail/python-dev/2003-March/033815.html>`__ Christian Tismer asked Guido and the list to take a look at a patch that would allow meta-types to have a __slots__. The patch was accepted and applied. `new bytecode results <http://mail.python.org/pipermail/python-dev/2003-March/033817.html>`__ Damien Morton continues on his quest to get performance boosts from fiddling with the eval loop contained in `ceval.c`_ and trying out various opcode ideas. It was pointed out that pystone_ is a good indicator of how Zope_ will perform on a new box. It was also stated by Tim Peters that since it is such an atypical test that it helps to make sure any improvements you make *really* do make an improvement. Damien also requested more people contribute statistical information to Skip Montanaro's stat server (more info at http://manatee.mojam.com/~skip/python/ ). .. ceval.c: .. _pystone: .. _Zope: http://www.zope.org/ `module extension search order - can it be changed? <http://mail.python.org/pipermail/python-dev/2003-March/033826.html>`__ This was discussed in the `last summary`_. Tim Peters mentioned how he doesn't use linecache_ often and that it's printing out of date info is not of any great use for tracebacks. .. _linecache: http://www.python.org/dev/doc/devel/lib/module-linecache.html `JUMP_IF_X opcodes <http://mail.python.org/pipermail/python-dev/2003-March/033823.html>`__ Damien Morton, still on the prowl for better opcodes, suggested introducing opcodes that combined branching opcodes and POP_TOP (which pops the top of the interpreter stack)¬?and did the pop based on the truth value of what was being tested. Neal Norwitz suggested that instead the branching instructions just always pop the stack. But then Raymond Hettinger came up with prediction macros that give a great speed boost to loops and conditionals by checking if the next opcode is one that normally follows the current opcode. If it does, it skips going through the eval loop for the next opcode, thus saving on overhead. If all of this cool opcode stuff that Damien keeps doing interests you, you will want to read `opcode.h`_, `ceval.c`_, and learn how to use the dis_ module. .. _opcode.h: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/python/python/dist/src/Inclu… .. _ceval.c: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/python/python/dist/src/Pytho… .. _dis: http://www.python.org/dev/doc/devel/lib/module-dis.html `Fun with timeit.py <http://mail.python.org/pipermail/python-dev/2003-March/033826.html>`__ A new module named timeit_ was added to the stdlib at the request of Jim Fulton. The module times the execution of code snippets. Guido timed the execution of going through a 'for' loop a million times with interpreters from Python 1.3 up to the current CVS (2.3a2 with patches up to that point). The result was that CVS was the fastest by a large margin. .. _timeit: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/python/python/dist/src/Lib/t… `Pre-PyCon sprint ideas <http://mail.python.org/pipermail/python-dev/2003-March/033827.html>`__ I asked the list to suggest ideas to sprint on at PyCon_. `More Zen <http://mail.python.org/pipermail/python-dev/2003-March/033828.html>`__ Words of wisdom from Raymond Hettinger that everyone should read. And if you have never read Raymond's `School of Hard Knocks`_ email you owe yourself to stop whatever you are doing and read it **now**. I can personally vouch that email is right on the money; I have experienced (or suffered, depending on your view =) every single thing on that list sans writing a PEP (although writing the Summary is starting to be enough writing to be equal =) . .. _School of Hard Knocks: http://mail.python.org/pipermail/python-dev/2002-September/028725.html `xmlrpclib <http://mail.python.org/pipermail/python-dev/2003-March/033837.html>`__ : `xmlrpclib: Apology <http://mail.python.org/pipermail/python-dev/2003-March/033847.html>`__ Bill Bumgarner, the "hillbilly from the midwest of the US", asked if the xmlrpclib_ module was being maintained. The lesson was also learned to not call Fredrick Lundh "Fred" on the list since Fred L. Drake, Jr. tends to be associated with the name. =) .. _xmlrpclib: http://www.python.org/dev/doc/devel/lib/module-xmlrpclib.html `httplib SSLFile broken in CVS <http://mail.python.org/pipermail/python-dev/2003-March/033832.html>`__ Something got broken and fixed. `super() bug (?) <http://mail.python.org/pipermail/python-dev/2003-March/033846.html>`__ Samuele Pedroni thought he may have found a bug with super() but turned out it wasn't. `test_popen broken on Win2K <http://mail.python.org/pipermail/python-dev/2003-March/033857.html>`__ Win2k does not like quoting of commands when there is no space in the command as Tim Peters discovered. There were discussions on how to deal with this. The suggestion of coming up with an sh-like syntax that works on all platforms (like what tcl's exec command has) was suggsted. `Change in int() behavior <http://mail.python.org/pipermail/python-dev/2003-March/033863.html>`__ David Abrahams rediscovered the joys of the road to which leads to int/long unification when he noticed that ``isinstance(int(sys.maxint*2), int)`` returns False. This will not be an issue once we are farther down this road. `acceptability of asm in python code? <http://mail.python.org/pipermail/python-dev/2003-March/033868.html>`__ Damien Morton popped his optimizing head back up on python-dev asking if assembly code was acceptable in the core. As of right now there is none, but Tim Peters stated that if there was some that had "a huge speedup, on all programs" then it would be considered, although "on the weak end of maybe". Christian Tismer (who plays with assembly in Stackless_) warned against it because it could cause a compiler to not use optimizations. .. _Stackless: http://www.stackless.com/ `Internationalizing domain names <http://mail.python.org/pipermail/python-dev/2003-March/033869.html>`__ Martin v. L??wis asked someone to look over his patches to implement IDNA (International Domain Names in Applications) which allows non-ASCII characters in domain names. `VERSION in getpath.c <http://mail.python.org/pipermail/python-dev/2003-March/033882.html>`__ Guido explains to someone what compile variables are used to generate some compile-based search paths. `Where is OSS used? <http://mail.python.org/pipermail/python-dev/2003-March/033905.html>`__ Greg Ward asked what OSs use OSS_. .. _OSS: http://www.opensound.com/ossfree/ `Audio devices <http://mail.python.org/pipermail/python-dev/2003-March/033947.html>`__ Greg Ward asked for opinions on some API issues for ossaudiodev_. .. _ossaudiodev: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/python/python/dist/src/Modul… `bsddb3 test errors - are these expected? <http://mail.python.org/pipermail/python-dev/2003-March/033961.html>`__ Skip Montanaro asked if some errors from the testing of bsddb3_ on OS X were expected. .. _bsddb3: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/python/python/dist/src/Modul… `os.path.dirname misleading? <http://mail.python.org/pipermail/python-dev/2003-March/033980.html>`__ Kevin Altis was surprised to discover that `os.path.dirname`_ would return the tail end of a directory instead of an empty string when the argument to the function was just a directory name. .. _os.path.dirname: http://www.python.org/dev/doc/devel/lib/module-os.path.html#l2h-1443 `Care to sprint on the core at PyCon? <http://mail.python.org/pipermail/python-dev/2003-March/033999.html>`__ Me asking the world if they wanted to sprint on the core at the pre-PyCon sprint (if you do, read the email for details). `Iterable sockets? <http://mail.python.org/pipermail/python-dev/2003-March/034038.html>`__ Andrew McNamara wished that socket objects were iterable on a per-line basis without having to call makefile(). Guido said he would rather come up with a better abstraction for Python 3 and prototype it in Python 2.4 or later. `More int/long integration issues <http://mail.python.org/pipermail/python-dev/2003-March/034019.html>`__ David Abrahams noticed that range() and xrange() couldn't accept a long. It basically led to Guido stating he considers xrange() a mistake and wished it didn't exist now that we have iterators. But since getting rid of it would break code he can at least prevent it from gaining abilities. It also led to Guido mentioning again how he would like to prohibit shadowing of built-ins. `tzset <http://mail.python.org/pipermail/python-dev/2003-March/034062.html>`__ A new function, time.tzset(), was added to Python and the tests had failed under Windows. The tests and the ./configure check were changed as needed. `PyObject_New vs PyObject_NEW <http://mail.python.org/pipermail/python-dev/2003-March/033970.html>`__ Lesson of the thread: PyObject_NEW is only to be used in the core; use `PyObject_New()`_ for extension modules. .. _PyObject_New(): http://www.python.org/dev/doc/devel/api/allocating-objects.html `are NULL checks in Objects/abstract.c really needed? <http://mail.python.org/pipermail/python-dev/2003-March/034011.html>`__ ... They are not required, but they are there to protect you against poorly written extensions. Skip Montanaro subsequently suggested a --without-null-checks compile option. `PyEval_GetFrame() revisited <http://mail.python.org/pipermail/python-dev/2003-March/034052.html>`__ A possible API for manipulating the current frame was still being discussed.

1 0

ANN: discord 1.0 -- Python conversion of dates to Discordian
by Erik Max Francis March 19, 2003

March 19, 2003

Summary A simple module for converting dates from Gregorian to Discordian. Overview This is a very simple module which allows for conversion from normal dates (via 'time.time', 'time.localtime', etc.) to Discordian dates (a silly made-up dating system that divides a year into five seasons of 73 days each). The module can either be used as a standalone command line application (which prints the current date in Discordian form) or as a extension module. Getting the software The current version of discord is 1.0. The latest version of the software is available in a tarball here: http://www.alcyone.com/pyos/discord/discord-latest.tar.gz. The official URL for this Web site is http://www.alcyone.com/pyos/discord/. Requirements This module requires Python 2.0 or greater. License This code is released under the GPL. .... Release history - 1.0; 2003 Mar 18. Initial release. -- Erik Max Francis / max(a)alcyone.com / http://www.alcyone.com/max/ __ San Jose, CA, USA / 37 20 N 121 53 W / &tSftDotIotE / \ Nine worlds I remember. \__/ Icelandic Edda of Snorri Sturluson Maths reference / http://www.alcyone.com/max/reference/maths/ A mathematics reference.

1 0

ANNOUNCE: Pytables 0.4
by Francesc Alted March 18, 2003

March 18, 2003

Announcing PyTables 0.4 ----------------------- I'm happy to announce the first beta release of PyTables. It is labelled beta because it has been thoroughly tested, even in production environments, and it is getting fairly mature. Besides, from now on, the API will remain mostly stable, so you can start using PyTables now with the guarantee that your code will also work (well, mostly ;-) in the future. The large amount of unit tests included in PyTables will also ensure the backward compatibility as well as the quality of future releases will remain at least as good as it is now (although hopefully it should increase!). What's new ----------- - numarray objects (NumArray, CharArray and RecArray) supported - As a consequence of a large internal code redesign (numarray is at the core of PyTables now), performance has been improved by a factor of 10 (see "How Fast Is It?" section) - It consumes far less memory than previous version - Support for reading generic HDF5 files added (!) - Some bugs and memory leaks existing in 0.2 solved - Updated documentation - Added more unit tests (more than 200 now!) What it is ---------- In short, PyTables provides a powerful and very Pythonic interface to process table and array data. Its goal is to enable the end user to manipulate easily scientific data tables and Numerical and numarray Python objects in a persistent hierarchical structure. The foundation of the underlying hierarchical data organization is the excellent HDF5 library (http://hdf.ncsa.uiuc.edu/HDF5). A table is defined as a collection of records whose values are stored in fixed-length fields. All records have the same structure and all values in each field have the same data type. The terms "fixed-length" and strict "data types" seems to be quite a strange requirement for an interpreted language like Python, but they serve a useful function if the goal is to save very large quantities of data (such as is generated by many scientific applications, for example) in an efficient manner that reduces demand on CPU time and I/O resources. Quite a bit effort has been invested to make browsing the hierarchical data structure a pleasant experience. PyTables implements just two (orthogonal) easy-to-use methods for browsing. What is HDF5? ------------- For those people who know nothing about HDF5, it is is a general purpose library and file format for storing scientific data made at NCSA. HDF5 can store two primary objects: datasets and groups. A dataset is essentially a multidimensional array of data elements, and a group is a structure for organizing objects in an HDF5 file. Using these two basic constructs, one can create and store almost any kind of scientific data structure, such as images, arrays of vectors, and structured and unstructured grids. You can also mix and match them in HDF5 files according to your needs. How fast is it? --------------- PyTables can write table records between 20 and 30 times faster than cPickle and between 3 and 10 times faster than struct (it is a module present in the Standard Library); and retrieves information around 100 times faster than cPickle and between 8 and 10 times faster than struct. When compared with SQLite (http://www.sqlite.org/), one of the fastest (free) relational databases available, PyTables achieves between a 60% and 80% the speed of SQLite during selects of dataset sizes that fit in the O.S. filesystem memory cache. However, when those sizes does not fit in the cache (i.e. when dealing with large amounts of data), PyTables beats SQLite by a factor of 2 or even more (depending on the kind of record selected), and its performance in this case is only limited by the I/O speed of the disk subsystem. Go to http://pytables.sourceforge.net/doc/PyCon.html#section4 for a detailed description on the conducted benchmarks. Platforms --------- I'm using Linux as the main development platform, but PyTables should be easy to compile/install on other UNIX machines. This package has also passed all the tests on a UltraSparc platform with Solaris 7 and Solaris 8. It also compiles and passes all the tests on a SGI Origin2000 with MIPS R12000 processors and running IRIX 6.5. If you are using Windows and you get the library to work, please let me know. An example? ----------- At the bottom of this message there is some code that shows basic capabilities of PyTables. You may also look at http://pytables.sourceforge.net/tut/tutorial1-1.html and http://pytables.sourceforge.net/tut/tutorial1-2.html for online code. Web site -------- Go to the PyTables web site for downloading and more details: http://pytables.sf.net/ Share your experience --------------------- Let me know of any bugs, suggestions, gripes, kudos, etc. you may have. Have fun! -- Francesc Alted falted(a)openlc.org *-*-*-**-*-*-**-*-*-**-*-*- Small code example *-*-*-**-*-*-**-*-*-**-*-*-* from tables import * class Particle(IsDescription): identity = Col("CharType", 22, " ", pos = 0) # character String idnumber = Col("Int16", 1, pos = 1) # short integer speed = Col("Float32", 1, pos = 1) # single-precision # Open a file in "w"rite mode fileh = openFile("objecttree.h5", mode = "w") # Get the HDF5 root group root = fileh.root # Create the groups: group1 = fileh.createGroup(root, "group1") group2 = fileh.createGroup(root, "group2") # Now, create a table in "group0" group array1 = fileh.createArray(root, "array1", ["string", "array"], "String array") # Create 2 new tables in group1 table1 = fileh.createTable(group1, "table1", Particle) table2 = fileh.createTable("/group2", "table2", Particle) # Create the last table in group2 array2 = fileh.createArray("/group1", "array2", [1,2,3,4]) # Now, fill the tables: for table in (table1, table2): # Get the record object associated with the table: row = table.row # Fill the table with 10 records for i in xrange(10): # First, assign the values to the Particle record row['identity'] = 'This is particle: %2d' % (i) row['idnumber'] = i row['speed'] = i * 2. # This injects the Record values row.append() # Flush the table buffers table.flush() # Select actual data from table. # on entries where TDCcount field is greater than 3 and pressure less than 50 out = [ x['identity'] for x in table.iterrows() if x['idnumber'] > 3 and 4 < x['speed'] < 10 ] print out # Finally, close the file (this also will flush all the remaining buffers!) fileh.close()

1 0

[Module] md5_crypt/1.0
by Jure Koren March 18, 2003

March 18, 2003

md5_crypt/1.0 ------------- md5crypt, password hashing algorithm A very common algorithm for hashing passwords on modern unices (the kind your favourite linux distribution uses). Implemented in C for speed, wrapped in python for convenience. URL: http://aufbix.org/~i/python/ Download: http://aufbix.org/~i/python/md5_crypt-0.1.tar.gz License: Public Domain Platform: *nix Categories: Encryption/Encoding Jure Koren (jure(a)aufbix.org) http://aufbix.org/~i/python/ -- <a href="http://aufbix.org/~i/python/">md5_crypt/1.0</a> -- md5crypt, password hashing algorithm

1 0

A few more days to register for PyDon DC!
by Guido van Rossum March 18, 2003

March 18, 2003

Coming Friday is the *last day* to register for PyCon DC online. After that, the rates go up to $250, and you'll have to pay on-site. http://www.python.org/pycon/ Speakers! This applies to you too. Already registered? BOOK YOUR HOTEL ROOM NOW! Late March is cherry blossom time in DC, and hotels fill up quickly. Ditto for flights. We've already got over 200 attendees registered. Don't miss it! --Guido van Rossum (home page: http://www.python.org/~guido/)

1 0

Python UK conference Wikki up
by John Precedo March 18, 2003

March 18, 2003

A basic Wikki Wikki is up for the UK Python Conference at http://server.reportlab.com/accu-2003/moin.cgi/FrontPage. Could anyone who will be attending the conference please add their name to the Attendees page? This will be the place to discuss travel arrangements, sort out lifts and ride shares etc. We also plan to have organisation of the various short talks here. And of course since it is a Wikki, if you think of something else that should be included you can add it yourself. -- John Precedo (johnp(a)reportlab.com) Developer Reportlab Europe Ltd (http://www.reportlab.com)

1 0

ZODB4 alpha 1 release
by Jeremy Hylton March 17, 2003

March 17, 2003

We've released ZODB4 alpha 1, the first official release of the ZODB code from the Zope3 project. You can get it at http://www.zope.org/Products/ZODB4. This release contains essentially the same software that will be in the upcoming Zope3 milestone release. This version of ZODB is very different from ZODB3. The Persistent base class is a new-style class, allowing persistent objects to use many of the features of Python 2.2 new-style classes. There are still many changes planned for future versions of ZODB4, but the current release is stable enough to call an alpha. The current test suite passes with Python 2.2.2 and Python 2.3 CVS on both Linux and Windows (2k). It will be possible to migrate data out of a 4.0a1 database into some future version. This release contains the top-level persistence, transaction, and zodb packages, as well as zope.interface and zope.testing. The implementation depends on zope.interface, but only in fairly limited way. The zope.testing package is only used by a few unit tests. The zodb package includes FileStorage, two storages based on BerkeleyDB, and ZEO, a client-server protocol for ZODB. Jeremy

1 0

PyCon: Last week for pre-reg!
by Aahz March 17, 2003

March 17, 2003

Friday, March 21 is the deadline if you want to get the $200 pre-conference price. PyCon will cost $250 at the door, and there is no single-day rate. http://www.python.org/pycon/reg.html PyCon DC 2003 The first PyCon will be held 26-28 March, 2003, at George Washington University's Cafritz Conference Center in Washington DC. There will be a development sprint Mon/Tues before the conference. PyCon is a community-oriented conference targeting developers (both those using Python and those working on the Python project). It gives you opportunities to learn about significant advances in the Python development community, to participate in a programming sprint with some of the leading minds in the Open Source community, and to meet fellow developers from around the world. The organizers have worked hard to ensure that the conference be affordable and accessible to all. We look forward to seeing you there. -- Aahz (aahz(a)pythoncraft.com) <*> http://www.pythoncraft.com/ Register for PyCon now! http://www.python.org/pycon/reg.html -- Aahz (aahz(a)pythoncraft.com) <*> http://www.pythoncraft.com/ Register for PyCon now! http://www.python.org/pycon/reg.html

1 0

Kodos 1.0.0 released - a regular expression gui debugger for python
by stuff＠nonpoint.mailzilla.net March 17, 2003

March 17, 2003

Kodos 1.0.0 has been released and is available at: http://kodos.sourceforge.net Kodos is a regular expression designer, tester, debugger and validator that allows a developer to create and modify regular expressions against a test string. The intuitive interface allows the developer the ability to modify the regular expression (regex) and to see the effects against their test string in real-time. Key Features: - Matches can be easily viewed and each match can be seen distinctly - Regex groups and named groups are clearly displayed - Sample source code is shown so even python developers new to regular expressions can quickly add the produced regular expressions to their own projects. - Ability to load and save your test cases - Kodos relies on PyQt for the GUI elements. Features new to version 1.0.0: - Display in the "match tab" now automaticcaly scrolls to the selected match number (eliminates need to scroll manually to find the match). - Save File As dialog will now prompt if the selected file already exists (allowing you to replace the existing file or select another file). To read more detailed information, view screenshots and download Kodos please visit: http://kodos.sourceforge.net

1 0