[Python-Dev] defaultdict proposal round three
Alex Martelli
aleaxit at gmail.com
Tue Feb 21 02:46:06 CET 2006
More information about the Python-Dev mailing list
Tue Feb 21 02:46:06 CET 2006
- Previous message: [Python-Dev] defaultdict proposal round three
- Next message: [Python-Dev] defaultdict proposal round three
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Feb 20, 2006, at 5:05 PM, Raymond Hettinger wrote: > [Alex] >>> I see d[k]+=1 as a substantial improvement -- conceptually more >>> direct, "I've now seen one more k than I had seen before". > > [Guido] >> Yes, I now agree. This means that I'm withdrawing proposal A (new >> method) and championing only B (a subclass that implements >> __getitem__() calling on_missing() and on_missing() defined in that >> subclass as before, calling default_factory unless it's None). I >> don't >> think this crisis is big enough to need *two* solutions, and this >> example shows B's superiority over A. > > FWIW, I'm happy with the proposal and think it is a nice addition > to Py2.5. OK, sounds great to me. collections.defaultdict, then? Alex
- Previous message: [Python-Dev] defaultdict proposal round three
- Next message: [Python-Dev] defaultdict proposal round three
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list