[issue26547] Undocumented use of the term dictproxy in vars() documentation

2016-06-23 Thread Berker Peksag
Berker Peksag added the comment: Thanks, Julien. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ __

[issue26547] Undocumented use of the term dictproxy in vars() documentation

2016-06-23 Thread Roundup Robot
Roundup Robot added the comment: New changeset 79e4593ce746 by Berker Peksag in branch '3.5': Issue #26547: Remove outdated term dictproxy from vars() documentation https://hg.python.org/cpython/rev/79e4593ce746 New changeset 45544b868f7b by Berker Peksag in branch 'default': Issue #26547: Merge

[issue26547] Undocumented use of the term dictproxy in vars() documentation

2016-06-22 Thread Berker Peksag
Changes by Berker Peksag : -- nosy: +berker.peksag stage: -> patch review type: enhancement -> behavior versions: +Python 3.5, Python 3.6 ___ Python tracker ___

[issue26547] Undocumented use of the term dictproxy in vars() documentation

2016-03-12 Thread Martin Panter
Martin Panter added the comment: In Python 2, the class was called “dictproxy”, the repr() used “dict_proxy” with an underscore, and it is exposed as types.DictProxyType. So I guess that is where the term comes from. In Python 3.3, Issue 14386 renamed the class and repr() to “mappingproxy”, an

[issue26547] Undocumented use of the term dictproxy in vars() documentation

2016-03-12 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: I would add a space between "dict" and "proxy". -- nosy: +martin.panter, serhiy.storchaka ___ Python tracker ___ _

[issue26547] Undocumented use of the term dictproxy in vars() documentation

2016-03-12 Thread Julien
New submission from Julien: I spotted un undocumented term here : https://docs.python.org/3.5/library/functions.html#vars in: "Objects such as modules and instances have an updateable __dict__ attribute; however, other objects may have write restrictions on their __dict__ attributes (for exam