- Zope-Dev - Zope lists

Zope Tests: 4 OK, 1 Failed
by Zope Tests Summarizer 30 May '08

30 May '08

Summary of messages to the zope-tests list. Period Thu May 29 11:00:00 2008 UTC to Fri May 30 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Test failures ------------- Subject: FAILED (failures=1) : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Thu May 29 21:06:41 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009629.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Thu May 29 21:00:40 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009625.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Thu May 29 21:02:10 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009626.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Thu May 29 21:03:40 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009627.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Thu May 29 21:05:11 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009628.html

1 0

Zope2 porting Acquisition
by ranjith kannikara 29 May '08

29 May '08

Hello everyone, I came across an error in module Acquisition, while trying to port zope2 to python2.5. There was a discussion over the same topic in JAN-2008. In acquisition the wrapper compare is returning false irrespective of the parameters. >>> c = A() >>> b.c = c >>> b.c.d = c >>> b.c.d == c 1 >>> b.c.d == b.c 1 >>> b.c == c 1 here 1) b.c.d == c is returning false and 2) b.c.d == b.c returns 1 3) b.c == c returns false And the problem I stuck with was that in the comparisons 1 and 3 the function Wrapper_compare defined in _Acquisition.c is not even called. How a function (say Wrapper_compare) from a C-API is being called on reaching a line like >>> b.c.d == c .

2 2

Zope Tests: 4 OK, 1 Failed
by Zope Tests Summarizer 29 May '08

29 May '08

Summary of messages to the zope-tests list. Period Wed May 28 11:00:00 2008 UTC to Thu May 29 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Test failures ------------- Subject: FAILED (failures=1) : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Wed May 28 21:05:41 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009624.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Wed May 28 20:59:40 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009620.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Wed May 28 21:01:10 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009621.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Wed May 28 21:02:40 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009622.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Wed May 28 21:04:10 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009623.html

1 0

Status of "Better XML support for Page Templates"?
by Paul Winkler 28 May '08

28 May '08

Was any action ever taken on this? http://wiki.zope.org/zope3/BetterXMLSupportForPageTemplates I never even realized until today that all my browser:page templates are apparently loaded in HTML mode. (Tested in Zope 2.9.9 / Five 1.4.2 ) -- http://www.slinkp.com

2 1

buildout and broken Cheeseshop download URLs
by Jens Vagelpohl 28 May '08

28 May '08

Hi guys, Does zc.buildout and/or the default egg recipe have any way of overriding the download URL from the cheese shop if that URL is broken and I cannot reach the package maintainer? Thanks! jens

3 6

Zope Tests: 4 OK, 1 Failed
by Zope Tests Summarizer 28 May '08

28 May '08

Summary of messages to the zope-tests list. Period Tue May 27 11:00:00 2008 UTC to Wed May 28 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Test failures ------------- Subject: FAILED (failures=1) : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Tue May 27 21:10:39 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009619.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Tue May 27 21:04:38 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009615.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Tue May 27 21:06:09 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009616.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Tue May 27 21:07:39 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009617.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Tue May 27 21:09:09 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009618.html

3 2

Proposal to add docs section to all top level zope3 package buildouts
by Paul Carduner 27 May '08

27 May '08

Short Version: - Need to add docs section to all top level zope 3 packages' buildout configs - Requires minor modification of packages - Please object if you don't want me to make changes. Long Version: In my continued effort to make zope 3 documentation more accessible, I've come up with a buildout recipe that uses Sphinx to build documentation from the *.txt files of a package. I would like every package with documentation in it to start utilizing this buildout script. A few minor additions to each package's buildout.cfg and setup.py files are needed for the recipe to work. There also needs to be an index.txt file in the package's main source directory to serve as the "front page" for the generated documentation. I intend to make these changes to all top level zope3 packages which have documentation in them in the very near future unless someone objects. So if anyone objects to these changes, please voice your opinion now. To give you a better idea of the necessary changes, I've included a diff that makes the recipe work for zope.component. (note that the change to zcml.txt was needed for proper ReST syntax). Index: buildout.cfg =================================================================== --- buildout.cfg (revision 86938) +++ buildout.cfg (working copy) @@ -1,6 +1,6 @@ [buildout] develop = . -parts = test py +parts = test py docs find-links = http://download.zope.org/distribution/ [test] @@ -11,3 +11,8 @@ recipe = zc.recipe.egg interpreter = py eggs = ${test:eggs} + +[docs] +recipe = z3c.recipe.sphinxdoc +eggs = z3c.recipe.sphinxdoc + zope.component [docs] Index: src/zope/component/index.txt =================================================================== --- src/zope/component/index.txt (revision 0) +++ src/zope/component/index.txt (revision 0) @@ -0,0 +1,24 @@ +Welcome to zope.component's documentation! +========================================== + +Contents: + +.. toctree:: + :maxdepth: 2 + + README + event + factory + persistentregistry + registry + socketexample + zcml + + +Indices and tables +================== + +* :ref:`genindex` +* :ref:`modindex` +* :ref:`search` + Property changes on: src/zope/component/index.txt ___________________________________________________________________ Name: svn:eol-style + native Index: src/zope/component/zcml.txt =================================================================== --- src/zope/component/zcml.txt (revision 86938) +++ src/zope/component/zcml.txt (working copy) @@ -912,6 +912,8 @@ Protected utilities ~~~~~~~~~~~~~~~~~~~ +Not yet part of these tests:: + def testProtectedUtility(self): """Test that we can protect a utility. Index: setup.py =================================================================== --- setup.py (revision 86938) +++ setup.py (working copy) @@ -67,6 +67,7 @@ 'zope.proxy', 'zope.i18nmessageid', ], + docs = ['Sphinx'], test = ['zope.testing', 'ZODB3', 'zope.hookable', -- Paul Carduner http://www.carduner.net

5 6

Re: SVN: Products.GenericSetup/tags/1.4.1dev-r85170/ Tag for internal snapshot release
by Tres Seaver 27 May '08

27 May '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hanno Schlichting wrote: > Log message for revision 86959: > Tag for internal snapshot release I hope "internal" means that I never stumble on this egg *anywhere*: wouldn't we be better off if you just made a 1.4.1 release? 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 iD8DBQFIOu6f+gerLs4ltQ4RAlBHAKCfTDRELPyegOaf7vjUbXfSB6g8iQCgns2N U4uslt1Hkp4TaQLl+DvBtLU= =ldF4 -----END PGP SIGNATURE-----

4 3

Zope Tests: 4 OK, 1 Failed
by Zope Tests Summarizer 27 May '08

27 May '08

Summary of messages to the zope-tests list. Period Mon May 26 11:00:00 2008 UTC to Tue May 27 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Test failures ------------- Subject: FAILED (failures=1) : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Mon May 26 21:07:34 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009614.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Mon May 26 21:01:33 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009610.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Mon May 26 21:03:03 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009611.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Mon May 26 21:04:33 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009612.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Mon May 26 21:06:03 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009613.html

1 0

Zope and Storm (SQL)
by Jürgen kartnaller 26 May '08

26 May '08

There seems to be some interest on the use of SQL databases with Zope. Lovelysystems is now using SQL databases as the primary storage for their applications. We use Zope and Postgres with Storm as ORM. The main reason for switching to SQL database were speed issues with queries. Here is a short summary of my thougt's and experiences while using Storm and Zope for about 3 Month now. RelStorage: Relstorage doesn't solve the speed problems. Doing queries with SQL is much faster than doing it with ZODB. If you work with a lot and with large BTrees you need to load them all into the memory of each Zope client. This has to be done with Relstorage too. Indexes: You don't need to implement catalog indexes, this is all done on the database side. When implementing and using your content types, at first you don't need to think about indexes, later you optimize the database without touching your python code. A speed example : We had to find similar users based on items a user has collected. Doing this with ZODB took minutes to calculate for users with a lot of items. We had to implement a lot of code to do the calculation asynchronously to not block the users request. Doing the same with SQL was possible with a single (of course complex) query within 300ms, no async things needed, just implement the query and optimize the indexes on the server, finished ! Relstorage will not help you here. Content implementation: While we are porting our existing ZODB based packages to SQL, we found that implementing them with Storm is as easy as using ZODB. We still can use the full power of Zope's component architecture. This is because Storm objects are extremely easy to implement. You can implement a storm object like a Persistent object, just derive from Storm instead of Persistent, add __storm_table__ and define the properties as Storm properties. For me a big mistake when switching from ZODB to SQL is trying to use the container pattern at any cost. A container is nothing but a 1:N relation and this is exactly what an SQL database provides : Relations class Content(Storm): id = Int(primary=True) content = ReferenceSet(id, 'Contained.somethingId') c = Content() Now you can - add data : c.content.add(content) - iterate : for a in c.content: - search : c.content.find(...) - sort : c.content.find().sort_by(...) - do anything a Storm ResultSet is providing But of course it is possible to put an adapter around the Content class which will provide IContainer. Annotation: Annotations are 1:1 relations, so it's as easy as the above. We use annotations like simple adapters to other tables. class ToBeAnnotated(Storm): interface.implements(ICanHaveData) id = Int(primary=True) Note that the "annotated" storm table is implemented as an adapter : class Data(Storm): interface.implements(IData) interface.adapts(ICanHaveData) id = Int(primary=True) __parent__ = Reference(id, ToBeAnnotated.id) def _init__(self, context): # a dummy to make the adapter happy pass We can now register "Data" as an adapter. We use a special adapter factory like zope.annotation.factory to autocreate adapted content. def contentAdapter(table, autocreate=True): # an adapter on content for content contained in other tables. Just like # the annotation adapter, an instance is created if autocreate is True. adapts = component.adaptedBy(table) if adapts is None: raise TypeError("Missing 'zope.component.adapts' on table") @component.adapter(list(adapts)[0]) @interface.implementer(list(component.implementedBy(table))[0]) def getAdapter(context): unsafeContext = removeSecurityProxy(context) obj = getStore().find(table, table.__parent__ == unsafeContext).one() if obj is None and autocreate: obj = table(context) obj.__parent__ = context return obj return getAdapter Now you can define a factory for the adapter: dataFactory = contentAdapter(Data) And register "dataFactory" as an adapter. DublinCore: If you want to use the full DublinCore implementation from Zope you need to do a generic implementation. Usually only parts of the DublinCore interface is used. We usually implement IDCTimes and IDCDescriptiveProperties. All you need to do for this is : class DCStormContent(Storm): interface.implements(IDCTimes, IDCDescriptiveProperties) created = DateTime() modified = DateTime() title = Unicode() description = Unicode() That's it! You can now use IDCTimes and IDCDescriptiveProperties for your formlib form_fields. There are two way's to update "modified" : - write an event handler for ObjectModifiedEvent - do it on the database side with triggers I prefer using the event handler because the database trigger is doing the update only when writing to the database which can be to late. Schema's and Storm objects: We don't use schema's to create our Storm objects or the database table from it. Right now for us it is not worth the time to implement such a feature. Traversing and URL's: Usually our customers whant to have special URL's for their pages. In any way (ZODB or SQL) we need to implement special traverser's to provide the URL's. Usually we use z3c.traverser to do this. Because of the special URL's we also need to implement absolute URL adapters. Transaction handling: Storm already has a DataManager for zope's transaction package. All you need to do is to register a utility for each of the database you want to use. ZMI: Hmm, don't work out of the box. If really needed we build traversers for the ZMI. Data transparency: At any time you can use any database administration tool you like to directly view and/or manipulate you data in the database. Jürgen

9 17