[ZCM] [ZC] 1028/ 3 Comment "manage_afterClone called with wrong parameter"

[Collector: Zope Bugs, Features, and Patches ...]

Issue #1028 Update (Comment) "manage_afterClone called with wrong parameter"
 Status Pending, Zope/bug medium
To followup, visit:
  http://www.zope.org/Collectors/Zope/1028

==============================================================
= Comment - Entry #3 by efge on Jul 11, 2005 12:36 pm

That's the historic API and for good or bad we can't change it.
If you feel the docstring should be updated, please provide one.

________________________________________
= Comment - Entry #2 by bmathieu on Jul 11, 2005 9:08 am

As of Zope 2.7 and 2.8 this code in CopySupport has not changed. So, is this a bug or the expected behaviour/use case? 

If yes, some documentation or comment would be welcome, since the benefit of calling manage_afterClone on an object with itself passed in parameter instead of the original object is a bit obscure...

________________________________________
= Request - Entry #1 by evilsloot on Aug 28, 2003 9:16 pm


Uploaded:  "CopySupport.py"
 - http://www.zope.org/Collectors/Zope/1028/CopySupport.py/view
when copying an object in Zope, the manage_afterClone method is called on the new object with the new object as a parameter. the parameter in question should be a reference to the old object. The culprit is manage_pasteObjects in lib/python/OFS/CopySupport.py

a corrected version of the file (changing lines 158-170) was uploaded with this report.
==============================================================