diff options
| author | Ned Deily <nad@python.org> | 2018-06-11 02:41:09 (GMT) |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-06-11 02:41:09 (GMT) |
| commit | 12c6cdf4d16078aa09de32a39193c8161177b39d (patch) | |
| tree | 3c9b1a8e715db2270bfa8762b86555ea1a859117 /Doc | |
| parent | ef057bfb06cae0718e6d708061649d2e3983e2ef (diff) | |
| download | cpython-12c6cdf4d16078aa09de32a39193c8161177b39d.zip cpython-12c6cdf4d16078aa09de32a39193c8161177b39d.tar.gz cpython-12c6cdf4d16078aa09de32a39193c8161177b39d.tar.bz2 | |
bpo-33745: Add What's New for empty function docstring change. (GH-7611)
Diffstat (limited to 'Doc')
| -rw-r--r-- | Doc/whatsnew/3.7.rst | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/Doc/whatsnew/3.7.rst b/Doc/whatsnew/3.7.rst index 81ef032..297d9fa 100644 --- a/Doc/whatsnew/3.7.rst +++ b/Doc/whatsnew/3.7.rst @@ -2431,3 +2431,8 @@ sufficient to both emit :exc:`BytesWarning` messages and have them converted to exceptions. Instead, the flag must be set (to cause the warnings to be emitted in the first place), and an explicit ``error::BytesWarning`` warnings filter added to convert them to exceptions. + +Due to a change in the way docstrings are handled by the compiler, the +implicit ``return None`` in a function body consisting solely of a docstring +is now marked as occurring on the same line as the docstring, not on the +function's header line. |