[Zope-dev] After migrate to 2.10.1 ManagableIndex throws TraversalErrors
I'm migrating the Zenoss code to Zope 2.10.1. I've moved to Five 1.5.1,
CMFCore 1.6.2. Does anyone know if there's a quick fix for this problem?
Traceback (most recent call last):
File "/usr/local/zenoss/Products/ZenEvents/zenxevent.py", line 87, in ?
z = ZenXEvent()
File "/usr/local/zenoss/Products/ZenEvents/zenxevent.py", line 37, in __init__
EventServer.__init__(self)
File "/usr/local/zenoss/Products/ZenEvents/EventServer.py", line 69, in
__init__
component=self.name))
File "/usr/local/zenoss/Products/ZenEvents/EventServer.py", line 105, in
sendEvent
self.zem.sendEvent(evt)
File "/usr/local/zenoss/Products/ZenEvents/MySqlSendEvent.py", line 52, in
sendEvent
event = self.applyEventContext(event)
File "/usr/local/zenoss/Products/ZenEvents/MySqlSendEvent.py", line 141, in
applyEventContext
device = devices.findDevice(evt.device)
File "/usr/local/zenoss/Products/ZenModel/DeviceClass.py", line 351, in
findDevice
ret = self._getCatalog().evalAdvancedQuery(query)
File "/usr/local/zenoss/Products/AdvancedQuery/eval.py", line 40, in eval
rs = _eval(query, cat)
File "/usr/local/zenoss/Products/AdvancedQuery/eval.py", line 16, in _eval
rs = query._eval(_QueryContext(cat))
File "/usr/local/zenoss/Products/AdvancedQuery/AdvancedQuery.py", line 82, in
_eval
return context._applyIndex(self, term)
File "/usr/local/zenoss/Products/AdvancedQuery/AdvancedQuery.py", line 276, in
_applyIndex
return
_wrapLookup(cat.indexes[index].__of__(cat)._apply_index({index:spec})[0])
File "/usr/local/zenoss/Products/ManagableIndex/ManagableIndex.py", line 332,
in _apply_index
t = prenorm(t, None)
File "/usr/local/zenoss/Products/ManagableIndex/ManagableIndex.py", line 570,
in _prenormalizeTerm
return normalizer._normalize(value, object)
File "/usr/local/zenoss/Products/ManagableIndex/Evaluation.py", line 132, in
_normalize
return evaluator._evaluate(value,object)
File "/usr/local/zenoss/Products/ManagableIndex/Evaluation.py", line 86, in
_evaluate
v= EvalAndCall.inheritedAttribute('_evaluate')(self,value,object)
File "/usr/local/zenoss/Products/ManagableIndex/Evaluation.py", line 58, in
_evaluate
return expr(context)
File "usr/local/zenoss/lib/python/zope/tales/expressions.py", line 217, in
__call__
File "usr/local/zenoss/lib/python/Products/PageTemplates/Expressions.py", line
122, in _eval
File "usr/local/zenoss/lib/python/zope/tales/expressions.py", line 124, in
_eval
File "usr/local/zenoss/lib/python/Products/PageTemplates/Expressions.py", line
74, in boboAwareZopeTraverse
File "usr/local/zenoss/lib/python/zope/traversing/adapters.py", line 161, in
traversePathElement
zope.traversing.interfaces.TraversalError: ('No traversable adapter found',
'captainapollo')
I've been told it may involve a rewrite of ManagableIndex to use Zope 3
adapters...any thoughts?
Ian McCracken
Zenoss, Inc.
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: RFC: Eggifying Zope's extension mechanism ("Products")
Daniel Nouri wrote: Philipp von Weitershausen wrote: For their upcoming versions, Zope 2 consuming platforms such as Plone are creating standard Zope3-style Python packages while still having Zope 2 products around. This proposal aims at unifying the deployment of products and Python packages into a Zope 2 instance alike by using Python eggs and their entry point system. See http://wiki.zope.org/zope2/EggifyingZopesExtensionMechanismQuotProductsQuot for the full proposal. Comments are appreciated. I plan on implementing it at the Camp5 BBQ sprint (http://www.openplans.org/projects/bbq-sprint) Sounds very good to me. However, I guess the biggest bulk of the work will be to make the existing Products out there eggs, which is quite a tedious task. It is also left up to those who develop those products. This proposal doesn't propose to change any existing products. It just gives consumer frameworks the ability to deploy products just like any other Python egg. A bit off topic: What about entry points for Zope 3 packages for their ZCML? Right now, when I easy_install a Zope 3 package, I still need to set up the ZCML by hand. I'm not sure that this is a sensible default. Jim has plans to * create configuration actions from Python instead of XML * use entry points as the "include" mechanism These plans were originally for Zope 3.4/2.11, not sure if it has been postponed by now. The PyCON 07 sprint may produce something. If Zope 3.4 gets it, Zope 2.11 will get it automatically. And yes, it will be very nice. All you then need is two entry points for a package and it's Zope2-enabled. -- http://worldcookery.com -- Professional Zope documentation and training Next Zope 3 training at Camp5: http://trizpug.org/boot-camp/camp5 ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: RFC: Acquisition and __parent__ pointers
On Wed, 2007-24-01 at 01:02 +0100, Philipp von Weitershausen wrote: > As for the implementation, I gave it my best shot in the > philikon-aq-and-__parent__ branch. My experience with C is limited, > especially when it comes to debugging. Help is therefore highly > appreciated. There's a reward waiting for whoever fixes the problem and > helps getting the branch merged to the trunk (see the proposal text). While I don't have the time (and probably not the C experience) required to help resolve this... I strongly support it getting completed :) So +1 from me. - Rocky -- Rocky Burt ServerZen Software -- http://www.serverzen.com News About The Server (blog) -- http://www.serverzen.net signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: RFC: Eggifying Zope's extension mechanism ("Products")
On Tue, 2007-23-01 at 23:58 +0100, Philipp von Weitershausen wrote: > For their upcoming versions, Zope 2 consuming platforms such as Plone > are creating standard Zope3-style Python packages while still having > Zope 2 products around. This proposal aims at unifying the deployment > of products and Python packages into a Zope 2 instance alike by using > Python eggs and their entry point system. > > See > http://wiki.zope.org/zope2/EggifyingZopesExtensionMechanismQuotProductsQuot > for the full proposal. Comments are appreciated. I plan on implementing > it at the Camp5 BBQ sprint (http://www.openplans.org/projects/bbq-sprint) A strong +1 here on the proposal. - Rocky -- Rocky Burt ServerZen Software -- http://www.serverzen.com News About The Server (blog) -- http://www.serverzen.net signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope Tests: 7 OK
Summary of messages to the zope-tests list. Period Tue Jan 23 12:00:00 2007 UTC to Wed Jan 24 12:00:00 2007 UTC. There were 7 messages: 7 from Zope Unit Tests. Tests passed OK --- Subject: OK : Zope-2.6 Python-2.1.3 : Linux From: Zope Unit Tests Date: Tue Jan 23 21:04:16 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007104.html Subject: OK : Zope-2.6 Python-2.3.6 : Linux From: Zope Unit Tests Date: Tue Jan 23 21:05:47 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007105.html Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Tue Jan 23 21:07:17 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007106.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Tue Jan 23 21:08:47 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007107.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Tue Jan 23 21:10:17 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007108.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Tue Jan 23 21:11:48 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007109.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Tue Jan 23 21:13:18 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007110.html ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: RFC: Eggifying Zope's extension mechanism ("Products")
Philipp von Weitershausen wrote: > For their upcoming versions, Zope 2 consuming platforms such as Plone > are creating standard Zope3-style Python packages while still having > Zope 2 products around. This proposal aims at unifying the deployment > of products and Python packages into a Zope 2 instance alike by using > Python eggs and their entry point system. > > See > http://wiki.zope.org/zope2/EggifyingZopesExtensionMechanismQuotProductsQuot > for the full proposal. Comments are appreciated. I plan on implementing > it at the Camp5 BBQ sprint (http://www.openplans.org/projects/bbq-sprint) Sounds very good to me. However, I guess the biggest bulk of the work will be to make the existing Products out there eggs, which is quite a tedious task. A bit off topic: What about entry points for Zope 3 packages for their ZCML? Right now, when I easy_install a Zope 3 package, I still need to set up the ZCML by hand. I'm not sure that this is a sensible default. Daniel ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
