Em Dom, 2005-11-27 às 21:26 +0100, Florent Guillaume escreveu:
> Dieter Maurer wrote:
> >>The first change is in the manage_pasteObjects method of CopyContainer.
> >>There are some _setObject and _delObject calls which grew a new
> >>suppress_events parameter. [...]
> > Several "Folder" like classes are likely to overwrite
> > "_setObject" and "_delObject".
> > Maybe, the code that calls these methods with an additional parameter
> > should be prepared to meet implementations that do not support
> > the extra parameter.
> Maybe. But on the other hand I'd rather not have object manager code
> slowed down and uglified to suit the negligibly small number of classes
> that are in this case, and that can be trivialy upgraded in a
> forward-compatible manner.
"Not gathering crust" is a nice an laudable goal, but so is "keep
I humbly suggest that the workaround code on ObjectManager be created
with a deprecation warning whenever it's triggered, declaring that the
backward compatibility will go away in, say, version 2.11, when it won't
be uglified and slowed down anymore.
You are, in essence, changing the API. IMHO this should take the same
deprecation treatment as everything else.
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -