Undeprecation of manage_afterAdd and manage_beforeDelete?
Hi. Zope 2 currently emits deprecation warnings about old-style event methods in OFS, for example manage_afterAdd and manage_beforeDelete. The deprecation warning states that these methods won't be called anymore in Zope 2.11. I would like to turn this deprecation warning into a discouraged warning, i.e. a deprecation warning that just states that the use of these methods is discouraged and you should use event subscribers, but any mentioning of a Zope version where this feature will be removed goes away. You can call it an endless deprecation warning as well. While event subscribers are certainly nicer, I don't see any realistic chance of refactoring all code in larger projects (like CMF and Plone) to move to events entirely in the next months or even years. Thoughts? Hanno
--On 6. Oktober 2007 18:07:51 +0200 Hanno Schlichting <plone@hannosch.info> wrote:
Hi.
Zope 2 currently emits deprecation warnings about old-style event methods in OFS, for example manage_afterAdd and manage_beforeDelete.
The deprecation warning states that these methods won't be called anymore in Zope 2.11.
I would like to turn this deprecation warning into a discouraged warning, i.e. a deprecation warning that just states that the use of these methods is discouraged and you should use event subscribers, but any mentioning of a Zope version where this feature will be removed goes away. You can call it an endless deprecation warning as well.
+1
While event subscribers are certainly nicer, I don't see any realistic chance of refactoring all code in larger projects (like CMF and Plone) to move to events entirely in the next months or even years.
Agreed. Andreas
Hanno Schlichting wrote at 2007-10-6 18:07 +0200:
I would like to turn this deprecation warning into a discouraged warning, i.e. a deprecation warning that just states that the use of these methods is discouraged and you should use event subscribers, but any mentioning of a Zope version where this feature will be removed goes away. You can call it an endless deprecation warning as well.
While event subscribers are certainly nicer, I don't see any realistic chance of refactoring all code in larger projects (like CMF and Plone) to move to events entirely in the next months or even years.
Thoughts?
+1 -- Dieter
Hanno Schlichting wrote:
Hi.
[..]
Thoughts?
+1 Raphael PS: ... not to mention the 700 add-ons that are out there for Plone alone ...
Hanno
_______________________________________________ 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 )
On 10/6/07, Hanno Schlichting <plone@hannosch.info> wrote:
While event subscribers are certainly nicer, I don't see any realistic chance of refactoring all code in larger projects (like CMF and Plone) to move to events entirely in the next months or even years.
No even years? Because there will be some time before Plone requires 2.11, you know. 3.0, which is just out, runs on 2.9 and 2.10. It's going to be until 3.5 that Plone even runs on 2.11, and probably not until Plone 4 until it requires it. That sais I don't really mind having deprecation warnings around for ever, there is so much cruft in Z2 anyway. ;-) We could probably wait with removing things until we can see that it really isn't used anymore. -- Lennart Regebro: Zope and Plone consulting. http://www.colliberty.com/ +33 661 58 14 64
Previously Lennart Regebro wrote:
On 10/6/07, Hanno Schlichting <plone@hannosch.info> wrote:
While event subscribers are certainly nicer, I don't see any realistic chance of refactoring all code in larger projects (like CMF and Plone) to move to events entirely in the next months or even years.
No even years? Because there will be some time before Plone requires 2.11, you know. 3.0, which is just out, runs on 2.9 and 2.10. It's going to be until 3.5 that Plone even runs on 2.11, and probably not until Plone 4 until it requires it.
Plone 3.0 needs Zope 2.10.3, anything earlier does not work. Plone 3.5 may very well require Zope 2.11. Wichert. -- Wichert Akkerman <wichert@wiggy.net> It is simple to make things. http://www.wiggy.net/ It is hard to make things simple.
On 10/9/07, Wichert Akkerman <wichert@wiggy.net> wrote:
Plone 3.0 needs Zope 2.10.3, anything earlier does not work.
Oh, I thought the idea was to always support two Zope versions? I'm happy to hear that this isn't the case. -- Lennart Regebro: Zope and Plone consulting. http://www.colliberty.com/ +33 661 58 14 64
Lennart Regebro wrote:
On 10/9/07, Wichert Akkerman <wichert@wiggy.net> wrote:
Plone 3.0 needs Zope 2.10.3, anything earlier does not work.
Oh, I thought the idea was to always support two Zope versions? I'm happy to hear that this isn't the case.
For 3.0 we needed the improved local components story. For 3.5 we'll most definitely want to have ZODB blob support, so each of them needs to require the newest Zope version. Hanno
participants (6)
-
Andreas Jung -
Dieter Maurer -
Hanno Schlichting -
Lennart Regebro -
Raphael Ritz -
Wichert Akkerman