Re: [Zope-dev] Developer meeting 2010-08-02 at 15:00 UTC
Hi, there notes from this weeks meeting should appear in a few minutes: http://docs.zope.org/zopetoolkit/zope-dev/zope-dev-20100803.html In short: Documentation improvements are making progress with Jens leading on making stuff accessible on doc.zope.org. Getting the packages in shape needs support with some initial bookkeeping (blueprints/bugs) and probably some coordinated effort at a sprint. Has everyone who was supposed to received their MSDN licenses by now? Adam is done with the Windows egg builder but due to PyPI issues and a hickup in doc.zope.org we couldn't review it. Christian -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ 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] docs.zope.org
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 8/5/10 00:16 , Willi Langenberger wrote: According to Jens Vagelpohl: before=$(svn info $ROOT | grep ^Last Changed Rev: | cut -d -f 4) svn up -q $ROOT after=$(svn info $ROOT | grep ^Last Changed Rev: | cut -d -f 4) I think svn info $ROOT doesnt give you the newest revision somewhere down the directory tree. You have to use something like svn info -R $ROOT | grep ^Last Changed Rev:| cut -d -f 4 | \ sort -k1n,1 | tail -1 (note the -R flag for the svn info command). Thanks Willi, I'll give that a try when I have a moment. I wouldn't be surprised if that was the case. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkxaW6gACgkQRAx5nvEhZLLmxACeLNo3ssUdKOHFRlQpYmnpuI2I B1IAn3Q0aAEqrIB++OtiJCrXf6Ew8meA =anjj -END PGP 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 )
[Zope-dev] Changing and migrating persistence structure
Hi, [I posted this to zodb-dev, but it seems that list isn't working at the moment(?) so I thought I'd try here too] 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 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. Now, I'd like to move to this structure: Registry(Persistent) | +-- Records | +-- BTree of Field | +-- BTree of values 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). 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 is the best way to manage this type of migration? In terms of API compatibility, I'd really like to keep plone.registry.Record as the name and module path of the record, since it is used by the API. The difference is that before it was persisted and returned by an API on the Registry. Now, it's constructed as needed on the fly from the internal data structure. The same applies to the various field types that derive from PersistentField, which are now Persistent, but won't be. There's code and documentation out there that use these. I'm less worried about the Records object, which was always an implementation detail, and the BTree-of-records, which will never have been accessed directly. Cheers, Martin ___ 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: 55 OK, 14 Failed, 1 Unknown
Summary of messages to the zope-tests list. Period Wed Aug 4 12:00:00 2010 UTC to Thu Aug 5 12:00:00 2010 UTC. There were 70 messages: 6 from Zope Tests, 1 from buildbot at enfoldsystems.com, 4 from buildbot at pov.lt, 13 from buildbot at winbot.zope.org, 11 from ccomb at free.fr, 35 from jdriessen at thehealthagency.com. Test failures - Subject: FAILED : Zope Buildbot / zope2 slave-osx From: jdriessen at thehealthagency.com Date: Wed Aug 4 09:52:53 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017889.html Subject: FAILED : Zope Buildbot / zope2 slave-osx From: jdriessen at thehealthagency.com Date: Wed Aug 4 15:04:16 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017894.html Subject: FAILED : Zope Buildbot / zope2 slave-osx From: jdriessen at thehealthagency.com Date: Wed Aug 4 15:52:54 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017895.html Subject: FAILED : Zope Buildbot / zope2 slave-osx From: jdriessen at thehealthagency.com Date: Wed Aug 4 16:52:52 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017898.html Subject: FAILED : Zope Buildbot / zope2 slave-osx From: jdriessen at thehealthagency.com Date: Wed Aug 4 17:52:53 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017901.html Subject: FAILED : winbot / ztk_dev py_244_win32 From: buildbot at winbot.zope.org Date: Wed Aug 4 22:08:10 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017915.html Subject: FAILED : winbot / ztk_dev py_254_win32 From: buildbot at winbot.zope.org Date: Wed Aug 4 22:15:11 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017917.html Subject: FAILED : winbot / ztk_dev py_265_win32 From: buildbot at winbot.zope.org Date: Wed Aug 4 22:21:41 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017918.html Subject: FAILED : winbot / ztk_dev py_265_win64 From: buildbot at winbot.zope.org Date: Wed Aug 4 22:28:21 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017919.html Subject: FAILED : ZTK 1.0dev / Python2.4.6 Linux 32bit From: ccomb at free.fr Date: Wed Aug 4 23:52:11 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017925.html Subject: FAILED : ZTK 1.0dev / Python2.6.4 Linux 32bit From: ccomb at free.fr Date: Wed Aug 4 23:53:22 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017926.html Subject: FAILED : ZTK 1.0dev / Python2.5.2 Linux 32bit From: ccomb at free.fr Date: Wed Aug 4 23:54:03 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017927.html Subject: FAILED : winbot / ZODB_dev py_270_win32 From: buildbot at winbot.zope.org Date: Thu Aug 5 03:10:04 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017937.html Subject: FAILED : winbot / ZODB_dev py_270_win64 From: buildbot at winbot.zope.org Date: Thu Aug 5 04:05:27 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017938.html Unknown --- Subject: [zodb-tests] buildbot failure in Enfold Systems on zodb-trunk-python-2.6-maestro From: buildbot at enfoldsystems.com Date: Thu Aug 5 03:03:38 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017936.html Tests passed OK --- Subject: OK : Zope Buildbot / zope2 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Wed Aug 4 09:54:34 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017890.html Subject: OK : Zope Buildbot / zope2 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Wed Aug 4 09:54:40 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017891.html Subject: OK : Zope Buildbot / zope2 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Wed Aug 4 14:54:34 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017892.html Subject: OK : Zope Buildbot / zope2 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Wed Aug 4 14:54:40 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017893.html Subject: OK : Zope Buildbot / zope2 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Wed Aug 4 15:54:34 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017896.html Subject: OK : Zope Buildbot / zope2 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Wed Aug 4 15:54:41 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017897.html Subject: OK : Zope Buildbot / zope2 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Wed Aug 4 16:54:38 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017899.html Subject: OK : Zope Buildbot / zope2 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Wed Aug 4 16:54:44 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017900.html Subject: OK : Zope Buildbot / zope2 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Wed Aug
Re: [Zope-dev] docs.zope.org
On Thu, Aug 05, 2010 at 08:35:20AM +0200, Jens Vagelpohl wrote: On 8/5/10 00:16 , Willi Langenberger wrote: According to Jens Vagelpohl: before=$(svn info $ROOT | grep ^Last Changed Rev: | cut -d -f 4) svn up -q $ROOT after=$(svn info $ROOT | grep ^Last Changed Rev: | cut -d -f 4) I think svn info $ROOT doesnt give you the newest revision somewhere down the directory tree. You have to use something like svn info -R $ROOT | grep ^Last Changed Rev:| cut -d -f 4 | \ sort -k1n,1 | tail -1 (note the -R flag for the svn info command). Thanks Willi, I'll give that a try when I have a moment. I wouldn't be surprised if that was the case. At first I thought that might've been the case, but when I went hunting for examples among my checkouts, I couldn't find one! E.g. the zopetoolkit/doc/ tree had a last change made change to source/conf.py, without touching anything in the parent directory, and svn info on doc/ listed Last Changed Rev correctly. 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 )
[Zope-dev] locale data inside zope.i18n
Hi, The zope.i18n has some locale data inside zope/i18n/locales/data. The global locale provider (zope.i18n.locales.locales) get data from this directory. What is the recommended approach to add a new locale XML file which is not available in CLDR: http://unicode.org/cldr/trac/browser/trunk/common/main/ I think the data available inside zope.i18n is bit outdated compared to what is available in Unicode site: http://unicode.org/Public/cldr/1.8.1/ How we are updating this database ? 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 )
Re: [Zope-dev] locale data inside zope.i18n
Hi. On Thu, Aug 5, 2010 at 6:42 PM, Baiju M mba...@zeomega.com wrote: The zope.i18n has some locale data inside zope/i18n/locales/data. The global locale provider (zope.i18n.locales.locales) get data from this directory. What is the recommended approach to add a new locale XML file which is not available in CLDR: http://unicode.org/cldr/trac/browser/trunk/common/main/ I'm not aware of any way for doing this. You'd have to dive into the details of the implementation and see if there's some plugin point you could use. I think the data available inside zope.i18n is bit outdated compared to what is available in Unicode site: http://unicode.org/Public/cldr/1.8.1/ How we are updating this database ? We aren't updating that database. It's completely outdated and has wrong information in many cases. I'd strongly recommend anyone for NOT using it. If you need ICU data in a Python project, I'd advise to use the much more popular Babel package, that is actually continuously updated. Hanno ___ 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] Developer meeting 2010-08-02 at 15:00 UTC
On Thu, Aug 5, 2010 at 8:22 AM, Christian Theune c...@gocept.com wrote: Has everyone who was supposed to received their MSDN licenses by now? I got eight mails with different subscribers ids a couple of days ago. All of them where delayed by three days, so by the time I got them, they had already expired. A support request sent to Microsoft got me a reply to try again with one of the numbers. This didn't work either. I sent in a new support request just now. Let's see if this ever gets me a working subscription. Hanno ___ 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 )
