I've been seeing the same sort of messages and many others.  I've assumed 
that they are due to the fact that nearly every Product will need some 
polishing as we approach the 2.10 and 2.11 releases.   Some of the 
diagnostics refer to subsystems in Zope itself which still use old rather 
than new mojo.  

The changes should somehow be coordinated and the various Products should 
be marked in some way to indicate their compatibility.  It would be 
helpful if there were a crib sheet indicating the changes (mostly 
mechanical) that need to be made since many systems have custom products 
that will need to be upgraded to the new protocols and hierarchy as well.

And, maybe this would be a good point to introduce eggs into the system, 
assuming that eggs are going to be part of Zope in the future. 


On Tue, 7 Mar 2006, Chris Withers wrote:

> Hi All,
> 
> I've started seeing warnings like this with an instance I'm moving from 
> Zope 2.7 to 2.9:
> 
> C:\Zope\2.9.1\lib\python\OFS\subscribers.py:74: DeprecationWarning: 
> Products.CookieCrumbler.CookieCrumbler.CookieCrumbler.manage_afterAdd is 
> deprecated and will be removed in Zope 2.11, you should use event 
> subscribers instead, and meanwhile mark the class with 
> <five:deprecatedManageAddDelete/>
>    DeprecationWarning)
> 
> Is there an example of exactly what I need to add and where?
> 
> cheers,
> 
> Chris
> 
> 

-- 

_______________________________________________
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 )

Reply via email to