On Apr 21, 2012 7:11 AM, "Nick Coghlan" <ncoghlan at gmail.com> wrote: >> The internal dictproxy class was recently exposed as types.MappingProxyType. >> Since it's not very discoverable that way, would anyone object if I > moved things around so it was exposed as collections.MappingProxy > instead? The main benefit to doing so is to get it into the table of > specialised container types at the top of the collections module docs > [1]. A discussion on this played out in http://bugs.python.org/issue14386. -eric >> [1] http://docs.python.org/dev/library/collections >> Cheers, > Nick. >> -- > Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: http://mail.python.org/mailman/options/python-dev/ericsnowcurrently%40gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20120421/ac90eed2/attachment.html>