Raymond Hettinger wrote: > [Ian Bicking] > >>The question then is what the API should look like for such an object -- >>an ordered, multi-value dictionary. > > > May I suggest that multidict begin it's life as a cookbook recipe so that its > API can mature. There's already quite a few recipes out there. But I should probably collect them as well. http://www.voidspace.org.uk/python/odict.html http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/107747 http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/438823 http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/173072 http://urchin.earth.li/~twic/odict.py http://www.astro.washington.edu/owen/ROPython.html http://home.arcor.de/wolfgang.grafen/Python/Modules/Modules.html email.Message.Message http://cvs.eby-sarna.com/wsgiref/src/wsgiref/headers.py?view=markup Well, there's a few, mostly ordered, some multivalue. A comparison would be helpful, but maybe a little later. odict is probably the most filled-out, though it is probably more listish than I really would like. -- Ian Bicking / ianb at colorstudy.com / http://blog.ianbicking.org
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4