[Zope-dev] Request for review: z3c.recipe.i18n (branch: baijum-zcml-path)
Hi Roger, I have created a branch to add a small feature addition to i18n recipe (z3c.recipe.i18n) here: svn://svn.zope.org/repos/main/z3c.recipe.i18n/branches/baijum-zcml-path Now the value of `zcml` option could be specified as a path to ZCML file. The old behaviour, which was expecting a ZCML string is retained. Please let me know, if I can merge this branch to trunk and make a new release. Since this is feature addition, I will be giving version number as 0.8.0. Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope Tests: 35 OK, 6 Failed
Summary of messages to the zope-tests list. Period Fri Aug 6 12:00:00 2010 UTC to Sat Aug 7 12:00:00 2010 UTC. There were 41 messages: 6 from Zope Tests, 4 from buildbot at pov.lt, 13 from buildbot at winbot.zope.org, 8 from ccomb at free.fr, 10 from jdriessen at thehealthagency.com. Test failures - Subject: FAILED : winbot / ztk_dev py_244_win32 From: buildbot at winbot.zope.org Date: Fri Aug 6 22:08:21 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018030.html Subject: FAILED : winbot / ztk_dev py_254_win32 From: buildbot at winbot.zope.org Date: Fri Aug 6 22:15:19 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018032.html Subject: FAILED : winbot / ztk_dev py_265_win32 From: buildbot at winbot.zope.org Date: Fri Aug 6 22:21:48 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018033.html Subject: FAILED : winbot / ztk_dev py_265_win64 From: buildbot at winbot.zope.org Date: Fri Aug 6 22:28:35 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018034.html Subject: FAILED : winbot / ZODB_dev py_270_win32 From: buildbot at winbot.zope.org Date: Sat Aug 7 03:09:42 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018048.html Subject: FAILED : winbot / ZODB_dev py_270_win64 From: buildbot at winbot.zope.org Date: Sat Aug 7 04:05:05 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018049.html Tests passed OK --- Subject: OK : Zope 3.4 Known Good Set / py2.4-64bit-linux From: buildbot at pov.lt Date: Fri Aug 6 21:08:46 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018019.html Subject: OK : Zope 3.4 Known Good Set / py2.4-32bit-linux From: buildbot at pov.lt Date: Fri Aug 6 21:28:29 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018020.html Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Fri Aug 6 21:32:14 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018021.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Fri Aug 6 21:34:15 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018022.html Subject: OK : Zope-2.12 Python-2.6.5 : Linux From: Zope Tests Date: Fri Aug 6 21:36:15 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018023.html Subject: OK : Zope-2.12-alltests Python-2.6.5 : Linux From: Zope Tests Date: Fri Aug 6 21:38:15 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018024.html Subject: OK : Zope-trunk Python-2.6.5 : Linux From: Zope Tests Date: Fri Aug 6 21:40:15 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018025.html Subject: OK : Zope-trunk-alltests Python-2.6.5 : Linux From: Zope Tests Date: Fri Aug 6 21:42:15 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018026.html Subject: OK : Bluebream / Python2.4.6 32bit linux From: ccomb at free.fr Date: Fri Aug 6 22:06:10 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018027.html Subject: OK : Bluebream / Python2.5.2 32bit linux From: ccomb at free.fr Date: Fri Aug 6 22:06:20 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018028.html Subject: OK : Bluebream / Python2.6.4 32bit linux From: ccomb at free.fr Date: Fri Aug 6 22:06:22 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018029.html Subject: OK : Zope 3.4 Known Good Set / py2.5-64bit-linux From: buildbot at pov.lt Date: Fri Aug 6 22:09:15 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018031.html Subject: OK : Zope 3.4 Known Good Set / py2.5-32bit-linux From: buildbot at pov.lt Date: Fri Aug 6 22:29:14 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018035.html Subject: OK : winbot / ztk_10 py_244_win32 From: buildbot at winbot.zope.org Date: Fri Aug 6 22:36:44 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018036.html Subject: OK : winbot / ztk_10 py_254_win32 From: buildbot at winbot.zope.org Date: Fri Aug 6 22:44:10 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018037.html Subject: OK : winbot / ztk_10 py_265_win32 From: buildbot at winbot.zope.org Date: Fri Aug 6 22:51:04 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018038.html Subject: OK : winbot / ztk_10 py_265_win64 From: buildbot at winbot.zope.org Date: Fri Aug 6 22:58:07 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018039.html Subject: OK : winbot / ZODB_dev py_254_win32 From: buildbot at winbot.zope.org Date: Sat Aug 7 00:25:20 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018040.html Subject: OK : Zope 3.4.1 KGS / Python2.4.6 32bit linux From: ccomb at free.fr Date: Sat Aug 7 00:36:39 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018041.html Subject: OK : Zope 3.4.1 KGS / Python2.5.2 32bit linux From: ccomb
Re: [Zope-dev] Changing and migrating persistence structure
On Thu, Aug 5, 2010 at 2:36 AM, Martin Aspeli optilude+li...@gmail.com wrote:
...
I have a package (plone.registry) that currently has a persistent
structure like this:
Registry(Persistent)
|
+-- Records(Persistent)
|
+-- BTree of Record(Persistent)
|
+-- PersistentField(Persistent)
That is, a Registry is a persistent object containing a persistent
Records object that in turn contains a BTree of persistent Record
Since BTrees are mapping, I assume that you mean the values are
records and that the keys are something boring like strings or
integers.
I like to use mathematical notation when talking about BTrees and
sets, as in:
Registry
BTree {? - Record}
objects that contain a persistent PersistentField and a primitive
value.
This is quite inefficient, though, because it results in a lot of
object loads. On any given request, some of our projects load a dozen
or more values from the registry. Each is just a simple primitive, but
we need to load the full shebang to make it work.
Not sure what you mean by full shebang.
Now, I'd like to move to this structure:
Registry(Persistent)
|
+-- Records
|
+-- BTree of Field
|
+-- BTree of values
I'm foggy on what field and value are here or what your queries
are doing. Maybe this is just a distraction.
Here, there's only one Persistent object, plus the two BTrees: one
holding all the fields and one holding all the values. Records no
longer needs to be persistent (its attributes become part of the
parent Registry's _p_jar).
I wonder what role Records plays independent of the Registry.
I also wonder why it matters whether it is persistent or not.
Fields no longer need to be persistent
either, since they are in effect immutable objects. Values are
primitives anyway.
I've done this (in a branch) and it works for new sites. However, I'm
having a nightmare trying to migrate old sites. As soon as I access
anything that uses the registry, I get ZODB errors, because the
persistent structure is now different. In particular, it's trying to
read a value into e.g. a Records object that used to derive from
Persistent, but now no longer does.
What savings do you get by making Records non-persistent?
What is the best way to manage this type of migration?
Today, it probably makes the most sense to make new classes for the
non-persistemnt objects. You'll then need to write a script to
rebuild the data structures.
Jim
--
Jim Fulton
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Request for review: z3c.recipe.i18n (branch: baijum-zcml-path)
On Sat, Aug 07, 2010 at 03:51:20PM +0530, Baiju M wrote: Hi Roger, I have created a branch to add a small feature addition to i18n recipe (z3c.recipe.i18n) here: svn://svn.zope.org/repos/main/z3c.recipe.i18n/branches/baijum-zcml-path I'm not Roger, but I looked at http://zope3.pov.lt/trac/log/z3c.recipe.i18n/branches/baijum-zcml-path anyway. Now the value of `zcml` option could be specified as a path to ZCML file. The old behaviour, which was expecting a ZCML string is retained. I'm not sure it makes sense to me: if you make a mistake and your ZCML is not well-formed, it will be treated as a filename? I don't think IOError: [Errno 2] No such file or directory: 'include package=z3c.recipe.tests file=extract.zcml /' is very friendly, and could lead the user on a wild-goose chase assuming that extract.zcml is somehow missing in the z3c.recipe.tests package (instead of noticing the stray and removing it). I'd rather see an alternative option name zcml-file = /path/name Please let me know, if I can merge this branch to trunk and make a new release. Since this is feature addition, I will be giving version number as 0.8.0. Incidentally, can you use zcml = include file=/absolute/path/name / without specifying a package? In other words, is this just syntactic sugar for something that's already possible, or a way to do something that wasn't possible before? Regards, Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development signature.asc Description: Digital signature ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
