Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2012-April/118947.html below:

[Python-Dev] Expose dictproxy through collections rather than the types module?

• Previous message: [Python-Dev] Expose dictproxy through collections rather than the types module?
• Next message: [Python-Dev] Expose dictproxy through collections rather than the types module?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Sat, 21 Apr 2012 23:09:08 +1000, Nick Coghlan <ncoghlan at gmail.com> wrote:
> 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

The short answer is yes, someone would mind, which is why it is where it
is.  Read the ticket for more: http://bugs.python.org/issue14386.

--David

• Previous message: [Python-Dev] Expose dictproxy through collections rather than the types module?
• Next message: [Python-Dev] Expose dictproxy through collections rather than the types module?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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