On 10/9/07, Wichert Akkerman <[EMAIL PROTECTED]> 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
Previously Lennart Regebro wrote:
> On 10/6/07, Hanno Schlichting <[EMAIL PROTECTED]> 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 eve
On 10/6/07, Hanno Schlichting <[EMAIL PROTECTED]> 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 wil
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 t
--On 6. Oktober 2007 18:07:51 +0200 Hanno Schlichting <[EMAIL PROTECTED]>
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
anym
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
warn
