December 2008 - Zope-Dev

Changelog formatting [was: SVN: cmf.pt/trunk/ Preparing release.]
by Philipp von Weitershausen 24 Dec '08

24 Dec '08

Malthe Borch wrote: > Log message for revision 94141: > Preparing release. > > Changed: > U cmf.pt/trunk/CHANGES.txt > U cmf.pt/trunk/setup.py > > -=- > Modified: cmf.pt/trunk/CHANGES.txt > =================================================================== > --- cmf.pt/trunk/CHANGES.txt 2008-12-17 11:44:23 UTC (rev 94140) > +++ cmf.pt/trunk/CHANGES.txt 2008-12-17 12:52:37 UTC (rev 94141) > @@ -1,7 +1,7 @@ > Changelog > ========= > > -In next release > +cmf.pt 0.2 (released 12/17/2008) I've noticed you're using the U.S. date format here which we discourage due to its ambiguity (in this case it happens not to be ambiguous, but that's just coincidence). The preferred format is the ISO 8601 dash notation (YYYY-MM-DD). This and other things, such as the proper formatting of changelogs, are documented in a guide called "Maintaining Software in the Zope Software Repository" [1] of which "Releasing Software" [2] is a chapter. I admit they're not in the most public place, I'm just the guy who wrote them (by codifying best practices). Anybody who'd like to put them somewhere more visible is most welcome to (e.g. the Grok folks have put the Releasing Software document on their website [3]). Happy holidays everyone, Philipp [1] http://svn.zope.org/*checkout*/Sandbox/philikon/foundation/maintaining-soft… [2] http://svn.zope.org/*checkout*/Sandbox/philikon/foundation/releasing-softwa… [3] http://grok.zope.org/documentation/how-to/releasing-software

2 1

C-extension in zope.i18nmessageid
by Malthe Borch 23 Dec '08

23 Dec '08

I've branched out this package and removed the C-extension. It's not documented in the package why a C-extension is needed or alternatively, what it benefits. If there are no objections, I will merge this into trunk shortly. \malthe

7 16

Re: [Zope-dev] [Checkins] SVN: zc.dict/branches/tlotze-blist/src/zc/dict/ordered.txt added a test to ensure the order is stored in a BList
by Gary Poster 23 Dec '08

23 Dec '08

Hi Thomas. Very cool that you are working on zc.dict + zc.blist. The updateOrder API is a sucky API for blists, as I'm sure you've realized. :-) FWIW, I seem to recall that Plone has a reasonable-to-nice API for changing order in containers, and the API would be able to take much better advantage of using blists for the ordering. I was intending to study that when I designed the new API (even if the Plone API were perfect, I would be wary of copying it because of GPL vs. ZPL, but maybe you could get them to relicense if you wanted it). You'd probably still want to keep updateOrder around, I guess, since that's the Zope 3 interface, but I would have documentation discouraging it. Gary

2 4

Zope Tests: 4 OK, 2 Failed
by Zope Tests Summarizer 23 Dec '08

23 Dec '08

Summary of messages to the zope-tests list. Period Mon Dec 22 12:00:00 2008 UTC to Tue Dec 23 12:00:00 2008 UTC. There were 6 messages: 6 from Zope Tests. Test failures ------------- Subject: FAILED (failures=2) : Zope-trunk Python-2.4.5 : Linux From: Zope Tests Date: Mon Dec 22 20:36:40 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010703.html Subject: FAILED (failures=2) : Zope-trunk Python-2.5.2 : Linux From: Zope Tests Date: Mon Dec 22 20:38:10 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010704.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Mon Dec 22 20:30:39 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010699.html Subject: OK : Zope-2.9 Python-2.4.5 : Linux From: Zope Tests Date: Mon Dec 22 20:32:09 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010700.html Subject: OK : Zope-2.10 Python-2.4.5 : Linux From: Zope Tests Date: Mon Dec 22 20:33:39 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010701.html Subject: OK : Zope-2.11 Python-2.4.5 : Linux From: Zope Tests Date: Mon Dec 22 20:35:09 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010702.html

1 0

Zope Tests: 4 OK, 2 Failed
by Zope Tests Summarizer 22 Dec '08

22 Dec '08

Summary of messages to the zope-tests list. Period Sun Dec 21 12:00:00 2008 UTC to Mon Dec 22 12:00:00 2008 UTC. There were 6 messages: 6 from Zope Tests. Test failures ------------- Subject: FAILED (failures=2) : Zope-trunk Python-2.4.5 : Linux From: Zope Tests Date: Sun Dec 21 20:36:57 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010697.html Subject: FAILED (failures=2) : Zope-trunk Python-2.5.2 : Linux From: Zope Tests Date: Sun Dec 21 20:38:27 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010698.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Sun Dec 21 20:30:56 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010693.html Subject: OK : Zope-2.9 Python-2.4.5 : Linux From: Zope Tests Date: Sun Dec 21 20:32:27 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010694.html Subject: OK : Zope-2.10 Python-2.4.5 : Linux From: Zope Tests Date: Sun Dec 21 20:33:57 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010695.html Subject: OK : Zope-2.11 Python-2.4.5 : Linux From: Zope Tests Date: Sun Dec 21 20:35:27 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010696.html

1 0

Using zope.proxy for read-only instances
by Andreas Jung 22 Dec '08

22 Dec '08

Hi there, I am trying to figure out how to use zope.proxy for creating read-only proxy objects of arbitrary Python objects where only attributes can be accessed read-only (no write access to attributes, no calling of methods). Anyone with some example code? Andreas

2 3

Re: [Zope-dev] SVN: relstorage/tags/1.1-jarn5/1.1-jarn/ retag internal release
by Tres Seaver 22 Dec '08

22 Dec '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Laurence Rowe wrote: > Log message for revision 94219: > retag internal release > > Changed: > A relstorage/tags/1.1-jarn5/1.1-jarn/ > > -=- I don't think that meant what you meant it to mean. ;) Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver(a)palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJTyVK+gerLs4ltQ4RAkslAJ9kOttwCaX85Fjei9GORowmzSFSqACfQmnM wLeYKEsAcj04A0gjDbp2C7M= =zD/W -----END PGP SIGNATURE-----

1 0

Re: [Zope-dev] Fwd: Help with RelStorage ...
by Shane Hathaway 22 Dec '08

22 Dec '08

Gareth Bult wrote: > </ul>ConflictError: database conflict error (oid 0x183a, class > BTrees._OOBTree.OOBTree, serial this txn started with > 0x037a73fba6331d66 2008-12-09 12:11:38.953047, serial currently > committed 0x037ab7770a1993dd 2008-12-21 12:07:02.367167) </p></p> <hr > noshade="noshade"/> My guess is that mysqlproxy is simply caching excessively. I haven't yet used mysqlproxy, but I think RelStorage will need some more configuration parameters to work effectively with mysqlproxy and any MySQL replication solution. Shane

1 0

Zope Tests: 4 OK, 2 Failed
by Zope Tests Summarizer 21 Dec '08

21 Dec '08

Summary of messages to the zope-tests list. Period Sat Dec 20 12:00:00 2008 UTC to Sun Dec 21 12:00:00 2008 UTC. There were 6 messages: 6 from Zope Tests. Test failures ------------- Subject: FAILED (failures=2) : Zope-trunk Python-2.4.5 : Linux From: Zope Tests Date: Sat Dec 20 20:36:01 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010691.html Subject: FAILED (failures=2) : Zope-trunk Python-2.5.2 : Linux From: Zope Tests Date: Sat Dec 20 20:37:31 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010692.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Sat Dec 20 20:30:00 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010687.html Subject: OK : Zope-2.9 Python-2.4.5 : Linux From: Zope Tests Date: Sat Dec 20 20:31:31 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010688.html Subject: OK : Zope-2.10 Python-2.4.5 : Linux From: Zope Tests Date: Sat Dec 20 20:33:01 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010689.html Subject: OK : Zope-2.11 Python-2.4.5 : Linux From: Zope Tests Date: Sat Dec 20 20:34:31 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010690.html

1 0

Zope Tests: 4 OK, 2 Failed
by Zope Tests Summarizer 20 Dec '08

20 Dec '08

Summary of messages to the zope-tests list. Period Fri Dec 19 12:00:00 2008 UTC to Sat Dec 20 12:00:00 2008 UTC. There were 6 messages: 6 from Zope Tests. Test failures ------------- Subject: FAILED (failures=2) : Zope-trunk Python-2.4.5 : Linux From: Zope Tests Date: Fri Dec 19 20:35:50 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010685.html Subject: FAILED (failures=2) : Zope-trunk Python-2.5.2 : Linux From: Zope Tests Date: Fri Dec 19 20:37:20 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010686.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Fri Dec 19 20:29:49 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010681.html Subject: OK : Zope-2.9 Python-2.4.5 : Linux From: Zope Tests Date: Fri Dec 19 20:31:19 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010682.html Subject: OK : Zope-2.10 Python-2.4.5 : Linux From: Zope Tests Date: Fri Dec 19 20:32:50 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010683.html Subject: OK : Zope-2.11 Python-2.4.5 : Linux From: Zope Tests Date: Fri Dec 19 20:34:20 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010684.html

1 0