This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author rhettinger
Recipients asvetlov, daniel.urban, jpeel, pitrou, rhettinger
Date 2010-12-11.01:01:43
SpamBayes Score 1.6394952e-10
Marked as misclassified No
Message-id <1292029307.89.0.846638919494.issue10667@psf.upfronthosting.co.za>
In-reply-to
Content
I would like this API to "sit and cook" for a good while.  There are many possible ways to add more methods and most be end-up being YAGNI. 
Also, my experience with dict.fromkeys() is that a fair number of people get confused by alternative constructors.  So, at this point I have zero interest in adding from_items().

Am taking the C optimizations under advisement.  In the meantime, there is no need to keep submitting patch variations.  The question is less how-to-do-it and more a question of whether-to-do-it.  We try not to add an alternate C paths unless a feature is an important building block.  There is an on-going maintenance cost and a risk of slightly different behaviors (at a minimum, the tracebacks look different and the code can't be traced through pdb).  That being said, there is a nice speed-up to be had, so I'll give that some weight.
History
Date User Action Args
2010-12-11 01:01:48rhettingersetrecipients: + rhettinger, pitrou, asvetlov, daniel.urban, jpeel
2010-12-11 01:01:47rhettingersetmessageid: <1292029307.89.0.846638919494.issue10667@psf.upfronthosting.co.za>
2010-12-11 01:01:43rhettingerlinkissue10667 messages
2010-12-11 01:01:43rhettingercreate