From: Éric Araujo Date: Tue, 7 Jun 2011 22:47:49 +0000 (+0200) Subject: Remove outdated bit of advice (584f9c213a6d follow-up) X-Git-Tag: v3.2.1rc2~87^2~13^2~3 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=b8f2ad03805048f43723019aecbcf181fbf01549;p=thirdparty%2FPython%2Fcpython.git Remove outdated bit of advice (584f9c213a6d follow-up) --- diff --git a/Doc/documenting/markup.rst b/Doc/documenting/markup.rst index 57d9eeba1472..c005d0c9e700 100644 --- a/Doc/documenting/markup.rst +++ b/Doc/documenting/markup.rst @@ -98,11 +98,12 @@ following example shows all of the features of this directive type:: Spam or ham the foo. -The signatures of object methods or data attributes should always include the -type name (``.. method:: FileInput.input(...)``), even if it is obvious from the -context which type they belong to; this is to enable consistent -cross-references. If you describe methods belonging to an abstract protocol, -such as "context managers", include a (pseudo-)type name too to make the +The signatures of object methods or data attributes should not include the +class name, but be nested in a class directive. The generated files will +reflect this nesting, and the target identifiers (for HTML output) will use +both the class and method name, to enable consistent cross-references. If you +describe methods belonging to an abstract protocol such as context managers, +use a class directive with a (pseudo-)type name too to make the index entries more informative. The directives are: