[issue14386] Expose dictproxy as a public type

Raymond Hettinger report at bugs.python.org
Mon Mar 26 22:38:09 CEST 2012

Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

The weakref collections objects (sets, dicts, etc) were all put in a separate module and that has worked out well.  I suggest doing the same for proxy objects.

In maintaining the itertools module, I learned long ago that adding new tools to the module made the whole module more difficult to use (increasing the number of choices increases the complexity of choosing the correct tool).  I believe that same also applies to the collections module and have been very reserved about adding new types there.  

ISTM that exposing internal types such as dict_proxy or bound/unbound methods could be collected together or that various proxy types and tools could be collected together.  I don't feel that dict_proxy belongs with namedtuple, deques, or OrderedDicts.

As the module maintainer, I request that dict_proxy be put elsewhere.  Of course, as BDFL you are free to override that request.


Python tracker <report at bugs.python.org>

More information about the Python-bugs-list mailing list