mirror of
https://github.com/python/cpython.git
synced 2025-12-31 04:23:37 +00:00
gh-142411: Change documentation to reflect the new docstring adjustments in 3.13 (#142413)
This commit is contained in:
parent
ff52e90ea4
commit
f6b6a99aa5
2 changed files with 12 additions and 15 deletions
|
|
@ -340,8 +340,8 @@ are always available. They are listed here in alphabetical order.
|
|||
It is needed to unambiguous :ref:`filter <warning-filter>` syntax warnings
|
||||
by module name.
|
||||
|
||||
This function raises :exc:`SyntaxError` if the compiled source is invalid,
|
||||
and :exc:`ValueError` if the source contains null bytes.
|
||||
This function raises :exc:`SyntaxError` or :exc:`ValueError` if the compiled
|
||||
source is invalid.
|
||||
|
||||
If you want to parse Python code into its AST representation, see
|
||||
:func:`ast.parse`.
|
||||
|
|
|
|||
|
|
@ -1039,31 +1039,28 @@ blank, visually separating the summary from the rest of the description. The
|
|||
following lines should be one or more paragraphs describing the object's calling
|
||||
conventions, its side effects, etc.
|
||||
|
||||
The Python parser does not strip indentation from multi-line string literals in
|
||||
Python, so tools that process documentation have to strip indentation if
|
||||
desired. This is done using the following convention. The first non-blank line
|
||||
*after* the first line of the string determines the amount of indentation for
|
||||
the entire documentation string. (We can't use the first line since it is
|
||||
generally adjacent to the string's opening quotes so its indentation is not
|
||||
apparent in the string literal.) Whitespace "equivalent" to this indentation is
|
||||
then stripped from the start of all lines of the string. Lines that are
|
||||
indented less should not occur, but if they occur all their leading whitespace
|
||||
should be stripped. Equivalence of whitespace should be tested after expansion
|
||||
of tabs (to 8 spaces, normally).
|
||||
The Python parser strips indentation from multi-line string literals when they
|
||||
serve as module, class, or function docstrings.
|
||||
|
||||
Here is an example of a multi-line docstring::
|
||||
|
||||
>>> def my_function():
|
||||
... """Do nothing, but document it.
|
||||
...
|
||||
... No, really, it doesn't do anything.
|
||||
... No, really, it doesn't do anything:
|
||||
...
|
||||
... >>> my_function()
|
||||
... >>>
|
||||
... """
|
||||
... pass
|
||||
...
|
||||
>>> print(my_function.__doc__)
|
||||
Do nothing, but document it.
|
||||
|
||||
No, really, it doesn't do anything.
|
||||
No, really, it doesn't do anything:
|
||||
|
||||
>>> my_function()
|
||||
>>>
|
||||
|
||||
|
||||
.. _tut-annotations:
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue