[ python-Bugs-1095821 ] The doc for DictProxy is missing
SourceForge.net
noreply at sourceforge.net
Mon Jan 10 13:32:53 CET 2005
Bugs item #1095821, was opened at 2005-01-04 10:42
Message generated for change (Comment added) made by greg_ball
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1095821&group_id=5470
Category: Python Library
Group: Python 2.3
Status: Open
Resolution: None
Priority: 5
Submitted By: Colin J. Williams (cjwhrh)
Assigned to: Nobody/Anonymous (nobody)
Summary: The doc for DictProxy is missing
Initial Comment:
The types module has an entry for DictProxy. I am
unable to find any documentation.
----------------------------------------------------------------------
Comment By: Gregory H. Ball (greg_ball)
Date: 2005-01-10 07:32
Message:
Logged In: YES
user_id=11365
Currently the library reference contains minimal information
on internal objects; here's the entire text of the relevant
section:
"""
2.3.10.10 Internal Objects
See the Python Reference Manual for this information. It
describes stack frame objects, traceback objects, and slice
objects.
"""
Perhaps cell and dictproxy types should be added to the
language reference manual. On the other hand, it isn't
clear to me that absolute completeness is desirable. Any
language or application has some undocumented features; the
fact that they
are not documented is a signal to the user that their use is
not supported and they may go away without warning in future
versions.
----------------------------------------------------------------------
Comment By: Colin J. Williams (cjwhrh)
Date: 2005-01-09 21:09
Message:
Logged In: YES
user_id=285587
I suggest that it would be better to indicate the purpose
and usage of both CellType in the Library Reference. If one
is to keep it under the pillow, it should be complete and
uptodate.
Colin W.
----------------------------------------------------------------------
Comment By: Gregory H. Ball (greg_ball)
Date: 2005-01-09 11:48
Message:
Logged In: YES
user_id=11365
DictProxy is an implementation detail, perhaps it should
have been left out of types. I notice there is no CellType
in there.
(you can obtain this type like so:)
>>> type((lambda x: lambda: x)(1).func_closure[0])
<type 'cell'>
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1095821&group_id=5470
More information about the Python-bugs-list
mailing list