On Mon, Jun 18, 2007 at 07:22:20PM +0300, Marius Gedminas wrote: > On Mon, Jun 18, 2007 at 12:20:57PM +0200, Christophe Combelles wrote: > > Hi, > > > > I've experienced a dangerous behaviour with namechoosers : > > > > If the namechooser computes a name which is the same as the current name, > > the object is deleted! > > > > This is simple to reproduce : > > - register a name chooser that only returns "foobar" > > - create your object → ok it's name is foobar > > - from the Contents view of it's container, try to rename it (with a > > different name) > > - → deleted > > > > Someone should try to reproduce that, to be sure that's not a side effect > > of my app, but I don't think so. > > I can reproduce it with a unit test:
I've added this to the bug tracker so it doesn't get lost: https://bugs.launchpad.net/zope3/+bug/123532 Marius Gedminas -- Ambition is a poor excuse for not having enough sense to be lazy.
signature.asc
Description: Digital signature
_______________________________________________ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
