diff options
| author | Éric Araujo <merwok@netwok.org> | 2011-06-04 16:35:04 (GMT) |
|---|---|---|
| committer | Éric Araujo <merwok@netwok.org> | 2011-06-04 16:35:04 (GMT) |
| commit | 3322a255320582d4ce67b14fe358adc4dc121db7 (patch) | |
| tree | 1fbf1fd87ac0533e594f3fadc365557cfc6bf9b3 /Doc/documenting | |
| parent | 7d214018119eeee43abc14db6385a2b684d1e4f8 (diff) | |
| download | cpython-3322a255320582d4ce67b14fe358adc4dc121db7.zip cpython-3322a255320582d4ce67b14fe358adc4dc121db7.tar.gz cpython-3322a255320582d4ce67b14fe358adc4dc121db7.tar.bz2 | |
Remove outdated bit of advice (c882b5ff92d9 follow-up)
Diffstat (limited to 'Doc/documenting')
| -rw-r--r-- | Doc/documenting/markup.rst | 11 |
1 files changed, 6 insertions, 5 deletions
diff --git a/Doc/documenting/markup.rst b/Doc/documenting/markup.rst index 6db8545..4f1fcae 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: |