--On 9. November 2005 20:41:24 +0100 Dieter Maurer <[EMAIL PROTECTED]>
wrote:
Florent Guillaume wrote at 2005-11-9 16:17 +0100:
...
To make sure that CMF 1.5.5 will play well with Five 1.2, I have to
make sure that no method manage_afterAdd redoes a recursion that one
of its base classes wa
Dieter Maurer wrote:
Florent Guillaume wrote at 2005-11-9 16:17 +0100:
...
To make sure that CMF 1.5.5 will play well with Five 1.2, I have to
make sure that no method manage_afterAdd redoes a recursion that one
of its base classes was doing, as we have to be prepared to have the
base cla
Florent Guillaume wrote at 2005-11-9 16:17 +0100:
> ...
>To make sure that CMF 1.5.5 will play well with Five 1.2, I have to
>make sure that no method manage_afterAdd redoes a recursion that one
>of its base classes was doing, as we have to be prepared to have the
>base class monkey-patched t
On 9 Nov 2005, at 15:17, Florent Guillaume wrote:
Does someone have a problem with me doing that in the CMF 1.5
branch? All with tests of course.
Does this have to happen now? Can we compromise, keep it out of 1.5.5
and create a 1.5.6 in a month or so?
jens
__
To make sure that CMF 1.5.5 will play well with Five 1.2, I have to
make sure that no method manage_afterAdd redoes a recursion that one
of its base classes was doing, as we have to be prepared to have the
base class monkey-patched to use events, and have recursion done with
events.
Concr
The following supporters have open issues assigned to them in this collector
(http://www.zope.org/Collectors/CMF).
Assigned and Open
efge
- "CMFSetup: provide non-ascii im- and exports",
[Accepted] http://www.zope.org/Collectors/CMF/292
- "CMFSetup doesn't correctly detect DCWo
