[issue16498] Unwanted link between volatile and shelve storage

[Terry Cooper]

Terry Cooper added the comment:

This is easy to reply to.  You better believe I've tried printing gList1 and dBasis[163].  I've also scrapped a predecessor function named combo (which is included in the attachment) and written its successor, viz., "combine".  I bent over backwards to make sure that the two functions did NOTHING the same way.  Guess what.  Both combo and combine screw up exactly the same record that they aren't supposed to know about in exactly the same way.  So I'm pretty sure Python remembers that it originally got one ITEM on gList from dBasis[161].  So I think I know that the problem is to determine WHY Python remembers that.  Of course what oneo thinks one knows is always subject to revision--especially what one thinks one knows about the truth.

--Terry

-----Original Message-----
>From: Ezio Melotti <report at bugs.python.org>
>Sent: Nov 18, 2012 2:07 PM
>To: ttcooper at indy.net
>Subject: [issue16498] Unwanted link between volatile and shelve storage
>
>
>Ezio Melotti added the comment:
>
>> They are obviously not the same record
>
>Have you tried printing gList1 and dBasis[163], their repr and their ids?
>
>----------
>nosy: +ezio.melotti
>
>_______________________________________
>Python tracker <report at bugs.python.org>
><http://bugs.python.org/issue16498>
>_______________________________________

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue16498>
_______________________________________