[Python-Dev] defaultdict proposal round three (original) (raw)
Raymond Hettinger python at rcn.com
Tue Feb 21 20:33:53 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 ]
Then you will likely be happy with Guido's current version of the patch.
----- Original Message ----- From: "Crutcher Dunnavant" <crutcher at gmail.com> To: "Raymond Hettinger" <python at rcn.com> Cc: "Python Dev" <python-dev at python.org> Sent: Monday, February 20, 2006 8:57 PM Subject: Re: [Python-Dev] defaultdict proposal round three
in two ways:
- dict.get doesn't work for object dicts or in exec/eval contexts, and
- dict.get requires me to generate the default value even if I'm not going to use it, a process which may be expensive.
On 2/20/06, Raymond Hettinger <python at rcn.com> wrote:
[Crutcher Dunnavant ] >> There are many times that I want d[key] to give me a value even when >> it isn't defined, but that doesn't always mean I want to save that >> value in the dict.
How does that differ from the existing dict.get method?
Raymond
-- Crutcher Dunnavant <crutcher at gmail.com> littlelanguages.com monket.samedi-studios.com
- Previous message: [Python-Dev] defaultdict proposal round three
- Next message: [Python-Dev] defaultdict proposal round three
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]