- Zope-Announce - Zope lists

MyMediaManager 1.3rc1 released !
by Gitte Wange 06 Oct '03

06 Oct '03

MM Manager is pleased to announce a new release of My Media Manager! This release includes server plugins for both Real Media, Windows Media and Quicktime. In this release we have improved the GUI so it should be even more easy to use. And as usual we have fixed some minor bugs (a bug in getIcon in MediaEvent.py made the product break in Plone - this has also been fixed!) We hope that the community will use this release and report any bugs they may find either in our collector or at our mailing list (find these at our website: http://www.mmmanager.org) This release candidate should be stable to use but it misses some feedback from our community before we will label it as the final release. The release candidate can be found at http://zope.org/Members/gittew/MyMediaManager/MyMediaManager-1.3rc1/ My Media Manager is a free set of online management- and publishing-tools, which enables you to administer streaming media content on one or several media servers, through your standard webbrowser. My Media Manager is developed by MM Manager.org -- Gitte Wange Technical Manager Email: gitte(a)mmmanager.org Web: http://www.mmmanager.org Tlf: +45 36 46 20 02 Text areas must die, text areas must die. -- Ethan Mindlace Fremen: IPC10, Zope 3 Management Interface BOF.

1 0

ZODB 3.2 release candidate 1
by Jeremy Hylton 02 Oct '03

02 Oct '03

We are happy to announce that ZODB 3.2 release candidate 1 has been released. You can find it at the usual place: http://www.zope.org/Products/ZODB3.2. This release contains a few bug fixes since the ZODB 3.2b3 release last week. If no major bugs are found in the release candidate, we will make the final release next week with identical code. If there are bugs, we will do another release candidate next week. What is ZODB? It is the Zope Object Database. It provides an object-oriented database for Python that provides a high-degree of transparency. Applications can take advantage of object database features with few, if any, changes to application logic. ZODB includes features such as a pluggable storage interface, rich transaction support, and undo. ZODB 3.2 has a number of new features and improvements over ZODB 3.1: - improve performance and stability of ZEO - new ZEO authentication protocol - new configuration language, ZConfig, for databases, storages, and ZEO servers - many bug fixes - improved documentation - new daemon tools The most recent changes from the NEWS.txt file are included below. -- Jeremy Hylton <http://www.python.org/~jeremy/> What's new in ZODB3 3.2 release candidate 1 =========================================== Release date: 01-Oct-2003 Added a summary to the Doc directory. There are several new documents in the 3.2 release, including "Using zdctl and zdrun to manage server processes" and "Running a ZEO Server HOWTO." Fixed ZEO's protocol negotiation mechanism so that a client ZODB 3.1 can talk to a ZODB 3.2 server. Fixed a memory leak in the ZEO server. The server was leaking a few KB of memory per connection. Fixed a memory leak in the ZODB object cache (cPickleCache). The cache did not release two references to its Connection, causing a large cycle of objects to leak when a database was closed. Fixed a bug in the ZEO code that caused it to leak socket objects on Windows. Specifically, fix the trigger mechanism so that both sockets created for a trigger are closed. Fixed a bug in the ZEO storage server that caused it to leave temp files behind. The CommitLog class contains a temp file, but it was not closing the file. Changed the order of setuid() and setgid() calls in zdrun, so that setgid() is called first. Added a timeout to the ZEO test suite that prevents hangs. The test suite creates ZEO servers with randomly assigned ports. If the port happens to be in use, the test suite would hang because the ZEO client would never stop trying to connect. The fix will cause the test to fail after a minute, but should prevent the test runner from hanging. The logging package was updated to include the latest version of the logging package from Python CVS. Note that this package is only installed for Python 2.2. In later versions of Python, it is available in the Python standard library. The ZEO1 directory was removed from the source distribution. ZEO1 is not supported, and we never intended to include it in the release.

1 0

PyCon DC 2004: Call for Proposals
by PyCon Chair 01 Oct '03

01 Oct '03

[Please repost to local Python mailing lists.] Want to share your expertise? PyCon DC 2004 is looking for proposals to fill the formal presentation tracks. PyCon DC 2003 had a broad range of presentations, from reports on academic and commercial projects to tutorials and case studies, and we hope to extend that range this year. As long as the presentation is interesting and potentially useful to the Python community, it will be considered for inclusion in the program. The proposal deadline is December 1; the proposal submission system should be up by mid-October. We'll send out another notice with more info when the submission system goes live. Proposals should be 250-1000 words in text (plain or reST) or HTML. You may request either thirty or sixty minutes for your timeslot. Proposals will be accepted or rejected by January 1, 2004. If your proposal is accepted, you may include a companion paper for publication on the PyCon web site. If you don't want to make a formal presentation, there will be a significant amount of Open Space to allow for informal and spur-of-the-moment presentations for which no formal submission is required. There will also be several Lightning Talk sessions (five minutes or less). For more information, see http://www.python.org/pycon/dc2004/cfp.html 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 work to make the conference affordable and accessible to all. DC 2004 will be held March 24-26, 2004 in Washington, D.C. The keynote speaker is Mitch Kapor of the Open Source Applications Foundation (http://www.osafoundation.org/) There will be a four-day development sprint before the conference. We're looking for volunteers to help run PyCon. If you're interested, subscribe to http://mail.python.org/mailman/listinfo/pycon-organizers Don't miss any PyCon announcements! Subscribe to http://mail.python.org/mailman/listinfo/pycon-announce You can discuss PyCon with other interested people by subscribing to http://mail.python.org/mailman/listinfo/pycon-interest The central resource for PyCon DC 2004 is http://www.python.org/pycon/dc2004/ -- Aahz (aahz(a)pythoncraft.com) <*> http://www.pythoncraft.com/ "It is easier to optimize correct code than to correct optimized code." --Bill Harlan

1 0

CompositePage product
by Shane Hathaway 01 Oct '03

01 Oct '03

CompositePage is a new way to assemble pages for the World Wide Web. Through the use of Zope technology, browser-based drag and drop, and custom context menus, CompositePage makes it easy to visually combine page fragments into complete pages. This is an early release. CompositePage supercedes the PageDesign product and makes use of PDLib, a Javascript library, making the new product signficantly simpler than PageDesign. CompositePage is designed for browsers that support the DOM (Document Object Model) and CSS (Cascading Style Sheets) level 2: Mozilla, Internet Explorer 5+, Opera, Konqueror, etc. There may be browser compatibility glitches, but it should be possible to sort them out. Please send an email if you find any problems. This product is designed for Zope 2.6 or 2.7 and Python 2.1, 2.2, or 2.3. When used with Zope 2.7, it takes advantage of the new OrderedFolder support. http://hathaway.freezope.org/Software/CompositePage/ Shane

1 0

[ANN] PloneCollectorNG 0.10 available
by Andreas Jung 29 Sep '03

29 Sep '03

I am pleased to announce the release of PloneCollectorNG 0.10 (PCNG) PCNG is a bugtracking system for Plone. It is based on the concepts and ideas of CMFCollector and CMFCollectorNG but it is a complete re-write. This release implements more or less the same functionality as the latest release of CMFCollectorNG except email notifications, confidential workflow. One major highlight of this new version is the built-in TTW editor for Archetypes schemas. This means you can edit the complete fields for your issue (field types and widgets) through-the-web including the use of schemats etc. Another goal of the new implementation was to focus on security. So I dropped the old workflow and created a new one (which is much simpler). The codebase is very small and generic and therefore very much extensible for the future. My vision for PloneCollectorNG is: - create an enterprise bugtracking system - support multiple workflows - extend its functionality for issue tracking e.g. in call-centers etc. - add highlevel and high-quality reporting Wiki and Download: http://www.zope.org/Members/ajung/PloneCollectorNG Cheers, -aj

1 0

ZServerSSL latest
by Ng Pheng Siong 28 Sep '03

28 Sep '03

Hi, M2Crypto 0.12 snapshot 1 is now available. What's new: - Tested with Python 2.3. - ZServerSSL with client certificate authentication. - ZServerSSL for Zope 2.7.0b2. Get M2Crypto here: http://sandbox.rulemaker.net/ngps/m2/ As usual, feedback is welcome. Cheers. -- Ng Pheng Siong <ngps(a)netmemetic.com> http://firewall.rulemaker.net -+- Manage Your Firewall Rulebase Changes http://sandbox.rulemaker.net/ngps -+- Open Source Python Crypto & SSL -- Ng Pheng Siong <ngps(a)netmemetic.com> http://firewall.rulemaker.net -+- Manage Your Firewall Rulebase Changes http://sandbox.rulemaker.net/ngps -+- Open Source Python Crypto & SSL

1 0

[Warning] "No more ReadConflicts" patch can cause inconsistencies
by Dieter Maurer 27 Sep '03

27 Sep '03

Dear Zope community, I have to admit that my "No more ReadConflicts" patch can cause ZODB inconsistencies. Probability is low but not zero. Details can be found on <mailto:zodb-dev@zope.org>. This fault was revealed by one of the ZODB 3.1.2 InvalidationTests which can fail on high speed servers. The problem can not be fixed for ZODB 3.1. I will work on a patch for ZODB 3.2 which avoids this problem (by implementing part of Jeremy's MVCC proposal). Dieter

1 0

PyCon Announcement: Mitch Kapor is opening keynote speaker
by PyCon Chair 26 Sep '03

26 Sep '03

[Apologies to people who see this twice; there was a glitch in the original sending.] Mitch Kapor to Keynote PyCon DC 2004 ------------------------------------ Washington, DC, September 24, 2003 The Python Software Foundation announced today that Mitch Kapor will be the opening keynote speaker for their second US Python community conference next March. Mr. Kapor is well known as a co-founder of Lotus Development Corporation and as a co-founder and the first chairman of the San Francisco-based Electronic Freedom Foundation, and has been an active entrepreneur in information technology for many years. More recently he founded the Open Software Applications Foundation (OSAF - see http://www.osafoundation.org/) The OSAF is using Python to build Chandler, an open source Personal Information Manager. PyCon is a community-oriented conference for developers of Python applications and for those with an interest in the development of the Python programming language. It offers the opportunity to learn about significant advances in Python's uses and 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 work to make the conference affordable and accessible to all. Pycon DC 2004 will be held March 24-26, 2004 in Washington, D.C. There will be a four-day development sprint before the conference. Volunteers interested in helping to run PyCon should subscribe to the organizers mailing list at http://mail.python.org/mailman/listinfo/pycon-organizers Don't miss any PyCon announcements! Subscribe at http://mail.python.org/mailman/listinfo/pycon-announce You can discuss PyCon with other interested people by subscribing at http://mail.python.org/mailman/listinfo/pycon-interest The central resource for PyCon DC 2004 is http://www.python.org/pycon/dc2004/ -- Aahz (aahz(a)pythoncraft.com) <*> http://www.pythoncraft.com/ "It is easier to optimize correct code than to correct optimized code." --Bill Harlan

1 0

zetadb-0.8.1 released
by Santi Camps 25 Sep '03

25 Sep '03

zetadb is a zope product that allows a rapid application development (RAD) of relational database oriented web applications. It automatically generates transladable and user friendly zope objects to maintain data over the web. It also allow generation of data-filled OpenOffice documents. Using zetadb you will be able to develop professional intranet / extranet business applications 4 or 5 times faster than using other more generalistic tools / languages More information and download: http://zetadb.sourceforge.net Santi Camps

1 0

ZODB 3.2b3 released
by Jeremy Hylton 24 Sep '03

24 Sep '03

We released ZODB 3.2b2 on Tuesday evening. You can find it at the usual place: http://www.zope.org/Products/ZODB3.2 This release contains the last new work we plan to do before the ZODB 3.2 final release. We have fixed several bugs, including a deadlock problem that had been reported against 3.2b2. ZODB 3.2 has a number of new features and improvements over ZODB 3.1: - improve performance and stability of ZEO - new ZEO authentication protocol - new configuration language, ZConfig, for databases, storages, and ZEO servers - many bug fixes Please give this new release a try. We hope to have a final release soon, and bugs reported soon are more likely to get fixed before the final release. I've included the NEWS.txt summary of the most recent changes. Jeremy What's new in ZODB3 3.2 beta 3 ============================== Release date: 23-Sep-2003 Note: The changes listed for this release include changes also made in ZODB 3.1.x releases and ported to the 3.2 release. This version of ZODB 3.2 is not compatible with Python 2.1. Early versions were explicitly designed to be compatible with Zope 2.6. That plan has been dropped, because Zope 2.7 is already in beta release. Several of the classes in ZEO and ZODB now inherit from object, making them new-style classes. The primary motivation for the change was to make it easier to debug memory leaks. We don't expect any behavior to change as a result. A new feature to allow removal of connection pools for versions was ported from Zope 2.6. This feature is needed by Zope to avoid denial of service attacks that allow a client to create an arbitrary number of version pools. Fixed several critical ZEO bugs. - If several client transactions were blocked waiting for the storage and one of the blocked clients disconnected, the server would attempt to restart one of the other waiting clients. Since the disconnected client did not have the storage lock, this could lead to deadlock. It could also cause the assertion "self._client is None" to fail. - If a storage server fails or times out between the vote and the finish, the ZEO cache could get populated with objects that didn't make it to the storage server. - If a client loses its connection to the server near the end of a transaction, it is now guaranteed to get a ClientDisconnected error even if it reconnects before the transaction finishes. This is necessary because the server will always abort the transaction. In some cases, the client would never see an error for the aborted transaction. - In tpc_finish(), reordered the calls so that the server's tpc_finish() is called (and must succeed) before we update the ZEO client cache. - The storage name is now prepended to the sort key, to ensure a unique global sort order if storages are named uniquely. This can prevent deadlock in some unusual cases. Fixed several serious flaws in the implementation of the ZEO authentication protocol. - The smac layer would accept a message without a MAC even after the session key was established. - The client never initialized its session key, so it never checked incoming messages or created MACs for outgoing messags. - The smac layer used a single HMAC instance for sending and receiving messages. This approach could only work if client and server were guaranteed to process all messages in the same total order, which could only happen in simple scenarios like unit tests. Fixed a bug in ExtensionClass when comparing ExtensionClass instances. The code could raise RuntimeWarning under Python 2.3, and produce incorrect results on 64-bit platforms. Fixed bug in BDBStorage that cause lead to DBRunRecoveryErrors when a transaction was aborted after performing operations like commit version or undo that create new references to existing pickles. Fixed a bug in Connection.py that caused it to fail with an AttributeError if close() was called after the database was closed. The test suite leaves fewer log files behind, although it still leaves a lot of junk. The test.py script puts each tests temp files in a separate directory, so it is easier to see which tests are causing problems. Unfortunately, it is still to tedious to figure out why the identified tests are leaving files behind. This release contains the latest and greatest version of the BDBStorage. This storage has still not seen testing in a production environment, but it represents the current best design and most recent code culled from various branches where development has occurred. The Tools directory contains a number of small improvements, a few new tools, and README.txt that catalogs the tools. Many of the tools are installed by setup.py; those scripts will now have a #! line set automatically on Unix. Fixed bugs in Tools/repozo.py, including a timing-dependent one that could cause the following invocation of repozo to do a full backup when an incremental backup would have sufficed. A pair of new scripts from Jim Fulton can be used to synthesize workloads and measure ZEO performance: see zodbload.py and zeoserverlog.py in the Tools directory. Note that these require Zope. Tools/checkbtrees.py was strengthened in two ways: - In addition to running the _check() method on each BTree B found, BTrees.check.check(B) is also run. The check() function was written after checkbtrees.py, and identifies kinds of damage B._check() cannot find. - Cycles in the object graph no longer lead to unbounded output. Note that preventing this requires remembering the oid of each persistent object found, which increases the memory needed by the script.

1 0