From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> Date: Mon, 11 Jun 2018 03:00:17 +0000 (-0700) Subject: bpo-33745: Add What's New for empty function docstring change. (GH-7611) X-Git-Tag: v3.7.0rc1~15 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=14a190c88273fb22d9439bbed394f19f21e8a0f9;p=python bpo-33745: Add What's New for empty function docstring change. (GH-7611) (cherry picked from commit 12c6cdf4d16078aa09de32a39193c8161177b39d) Co-authored-by: Ned Deily --- diff --git a/Doc/whatsnew/3.7.rst b/Doc/whatsnew/3.7.rst index 81ef032f93..297d9fa312 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.