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