June 2008 - Zope-Dev

Zope Tests: 5 OK
by Zope Tests Summarizer 23 Jun '08

23 Jun '08

Summary of messages to the zope-tests list. Period Sun Jun 22 11:00:00 2008 UTC to Mon Jun 23 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Sun Jun 22 20:58:37 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009745.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Sun Jun 22 21:00:07 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009746.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Sun Jun 22 21:01:38 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009747.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Sun Jun 22 21:03:08 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009748.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Sun Jun 22 21:04:39 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009749.html

1 0

Zope Tests: 5 OK
by Zope Tests Summarizer 22 Jun '08

22 Jun '08

Summary of messages to the zope-tests list. Period Sat Jun 21 11:00:00 2008 UTC to Sun Jun 22 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Sat Jun 21 21:08:05 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009740.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Sat Jun 21 21:09:35 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009741.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Sat Jun 21 21:11:05 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009742.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Sat Jun 21 21:12:35 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009743.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Sat Jun 21 21:14:06 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009744.html

1 0

Zope Tests: 5 OK
by Zope Tests Summarizer 21 Jun '08

21 Jun '08

Summary of messages to the zope-tests list. Period Fri Jun 20 11:00:00 2008 UTC to Sat Jun 21 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Fri Jun 20 21:00:30 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009735.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Fri Jun 20 21:02:00 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009736.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Fri Jun 20 21:03:31 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009737.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Fri Jun 20 21:05:01 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009738.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Fri Jun 20 21:06:31 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009739.html

1 0

View component registration
by Malthe Borch 20 Jun '08

20 Jun '08

Currently views are registered as components providing zope.interface.Interface; this is unfortunate since other kinds of components may use the same specification, namely (context, request). An example of this is ``IAbsoluteURL``; it clashes with the resources view*. In the words of Christian Theune: "I think it looks like one should never ask for adaptions to Interface." I suggest we then register views as components providing ``zope.component.IView``; browser views should provide ``zope.publisher.interfaces.browser.IBrowserView``. \malthe *) ``zope.app.publisher.browser.resources.Resources``.

6 19

Zope Tests: 5 OK
by Zope Tests Summarizer 20 Jun '08

20 Jun '08

Summary of messages to the zope-tests list. Period Thu Jun 19 11:00:00 2008 UTC to Fri Jun 20 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Thu Jun 19 21:01:57 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009730.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Thu Jun 19 21:03:27 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009731.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Thu Jun 19 21:04:57 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009732.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Thu Jun 19 21:06:28 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009733.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Thu Jun 19 21:07:58 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009734.html

1 0

made zope.sqlalchemy work with SA 0.5beta1
by Martijn Faassen 19 Jun '08

19 Jun '08

Hi there, I've made zope.sqlalchemy work with SQLAlchemy 0.5 beta 1, recently released. This involved: * the 'transactional=True' argument has become 'autocommit=False' * various accesses that the tests were doing to get query.table and such didn't work anymore. I replaced them with direct accesses to the mapped classes. I've also added a CHANGES.txt and a CREDITS.txt, and made it so that the CHANGES.txt information is also uploaded to the cheeseshop. We'll be using the official guidelines for svn.zope.org management of this package for version numbers, and I've made adjustments there too. The official guidelines are only actually hosted on grok.zope.org to my knowledge, and they're here: http://grok.zope.org/documentation/how-to/releasing-software All of this work is on a branch: svn+ssh://svn.zope.org/repos/main/zope.sqlalchemy/branches/sqlalchemy-0.5-s… I'd like to merge the branch to the trunk as soon as possible, but I need Laurence's "go" first. Laurence, any chance we'll be doing a release for 0.4* from the trunk? Or we could delegate that work to a maintenance branch (if necessary) and aim for SA 0.5 support on the trunk now? Let me know and I'll merge the branch. Regards, Martijn

2 2

Extend specification of how to maintain the changelog
by Christian Theune 19 Jun '08

19 Jun '08

Hi, This post refers to Philipp's guide for `Maintaining software in the Zope software repository` [1]. I noticed that I kept getting confused about maintaining CHANGES.txt entries when merging bug fixes around, looked around a bit and thought I'd share my findings. First, I think we have a terminology issue as the standard form of 'ChangeLog' refers to individual changes, pretty much as what is recorded by subversion's log. (See [2] and [3].) What I understand from the Wikipedia entries for Changelog [4] and Release notes [5] is that what we record in the CHANGES.txt files is closer to release notes than a changelog. This is just an observation -- I'm happy with the actual content of what we use to put into the CHANGES.txt file. The core problem in maintenance is that I wasn't sure how to record bug fixes that are applied over multiple branches (trunk and maybe one or two maintenance branches). I discussed this a bit and found the following way that looks reasonable: - The CHANGES.txt is mainainted for each release series in their branch (obviously). - The first section marks the next released (as specified in [1]). - A change on a branch is recorded in the next unreleased section. (Merges of the same fix over multiple branches are not recorded in different places on the other branches.) This results in the following properties for the CHANGES.txt: - The trunk will contain sections for feature releases (e.g. 1.0, 1.1, ..) but not bugfix releases (e.g. 1.0.2). - Bug fixes will appear once in the feature release of the trunk (e.g. 1.1) and once in each individual dot release of the various maintenance branches that it went into (e.g. 1.0.y) - There is not individual "large" CHANGES.txt that appears to be a simple concatenation of the various changes on branches because we respect the tree-ness of maintenance branches. I find that Philipp's guide could be extended/clarified a bit more about this. Comments, suggestions, etc. welcome. Christian [1] http://svn.zope.org/*checkout*/Sandbox/philikon/foundation/maintaining-soft… [2] http://www.gnu.org/prep/standards/html_node/Change-Logs.html#Change-Logs [3] http://www.gnu.org/software/guile/changelogs/guile-changelogs_toc.html [4] http://en.wikipedia.org/wiki/Changelog [5] http://en.wikipedia.org/wiki/Release_notes -- Christian Theune · ct(a)gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1 Zope and Plone consulting and development

7 35

Zope Tests: 5 OK
by Zope Tests Summarizer 19 Jun '08

19 Jun '08

Summary of messages to the zope-tests list. Period Wed Jun 18 11:00:00 2008 UTC to Thu Jun 19 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Wed Jun 18 20:53:49 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009725.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Wed Jun 18 20:55:19 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009726.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Wed Jun 18 20:56:50 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009727.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Wed Jun 18 20:58:23 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009728.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Wed Jun 18 20:59:54 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009729.html

1 0

Re: [ZODB-Dev] Re: Advice on ZODB with large datasets
by Laurence Rowe 19 Jun '08

19 Jun '08

It's helpful to post your responses to the mailing list, that way when someone else has a similar problem in the future they'll be able to find the information. Inheriting from Persistent is also necessary to control the granularity of the database. Persistent objects are saved as separate `records` by ZODB. Other objects do not have a _p_oid attribute and have to be saved as part of their parent record. Laurence 2008/6/19 <AFoglia(a)princeton.com>: > Laurence Rowe wrote: >> >> AFoglia(a)princeton.com wrote: >> Does your record class inherit from persistent.Persistent? 650k integers + >> object pointers should only be of the order 10 Mb or so. It sounds to me >> like the record data is being stored in the btrees bucket directly. > > No, it does not. It's just a simple dictionary for the time being. > I assumed the BTree bucket would itself know to load the values only when > they are explicitly requested, and that the Persistence of the objects just > merely meant that the database didn't keep track of changes of nonpersistent > objects. I will try copying my dictionaries to Persistent Mappings for now. > >> Something like this should lead to smaller bucket objects where the record >> data is only loaded when you access the values of the btree: >> >> >>> from BTrees.IOBTree import IOBTree >> >>> bt = IOBTree() >> >>> from persistent import Persistent >> >>> class Record(Persistent): >> ... def __init__(self, data): >> ... super(Record, self).__init__() >> ... self.data = data >> ... >> >>> rec = Record("my really long string data") >> >>> bt[1] = rec > >

1 1

Zope Tests: 5 OK
by Zope Tests Summarizer 18 Jun '08

18 Jun '08

Summary of messages to the zope-tests list. Period Tue Jun 17 11:00:00 2008 UTC to Wed Jun 18 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Tue Jun 17 21:00:36 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009720.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Tue Jun 17 21:02:06 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009721.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Tue Jun 17 21:03:36 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009722.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Tue Jun 17 21:05:07 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009723.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Tue Jun 17 21:06:37 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009724.html

1 0