Hello,
Looking in the code it seems that this error could be raised in three
places. I think the error message ought to have specified which of the
three places, so it should have said something like:
XXXX.__init__: Could not create, pre-existing object had same key: YYYY
where XXXX = class name and YYYY = the duplicate key (hopefully).
Just looking at the code I can see a potential issue when XXXX =
DangleChain. I think the problem arises if you try and make a separate
Dangle run with the same chain but a different shiftList. Does that ring
a bell? (So possibly this is a weakness in the Dangle data model, I'll
have to ask Tim.)
Wayne
On Mon, 17 Oct 2011, Krisztina Feher wrote:
> Hi Wayne,
>
> what I showed was in the Python shell, no more.... But I check again in the
> evening.
>
> Krisztina
>
> --- On Sun, 10/16/11, Wayne Boucher <[log in to unmask]> wrote:
>
> From: Wayne Boucher <[log in to unmask]>
> Subject: Re: DANGLE error "Could not create, pre-existing object had
> same key"
> To: [log in to unmask]
> Date: Sunday, October 16, 2011, 10:08 PM
>
> Hello,
>
> Was there any kind of stack trace (in the Python shell)?
>
> Wayne
>
> On Sun, 16 Oct 2011, Krisztina Feher wrote:
>
> >
> >
>
>
>
|