I may have found a bug in the __setitem__ method of the maxdict class.
Since a dictionary is a mapping class, if an item is set that already
exists, it overwrites the previous. However, you are still appending that
item to _killkeys regardless.
In the case where 2 items with the same key were added and later removed due
to size constraints, the line in bold would throw an exception on the second
call.
By checking for the key existance, you handle that situation gracefully.
The item can still be removed from _killkeys, since it's the next to go
anyway.
Ryan
Original code (circa line 776):
if len(self)>=self.maxsize:
del self[self._killkeys[0]]
del self._killkeys[0]
dict.__setitem__(self, k, v)
self._killkeys.append(k)
Possible solution:
if len(self)>=self.maxsize:
if self.has_key(self._killkeys[0]):
del self[self._killkeys[0]]
del self._killkeys[0]
dict.__setitem__(self, k, v)
self._killkeys.append(k)
--
View this message in context:
http://www.nabble.com/cbook.py%2C-maxdict-class-key-checking-on-__setitem__-tp25090453p25090453.html
Sent from the matplotlib - devel mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
