[issue33477] Document that compile(code, 'exec') has different behavior in 3.7+

Matthias Bussonnier added the comment: Closing as the ast changes have been reverted. -- stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue33477] Document that compile(code, 'exec') has different behavior in 3.7+

Change by Matthias Bussonnier : -- keywords: +patch pull_requests: +6628 stage: -> patch review ___ Python tracker ___

[issue33477] Document that compile(code, 'exec') has different behavior in 3.7+

Matthias Bussonnier added the comment: Fair enough that what's new include things about Module > The first statement in their body is not considered as a docstring anymore. Note that this sentence read backward to me. I understand what is meant because I know

[issue33477] Document that compile(code, 'exec') has different behavior in 3.7+

INADA Naoki added the comment: Any comments? Would you close this issue? -- ___ Python tracker ___

[issue33477] Document that compile(code, 'exec') has different behavior in 3.7+

INADA Naoki added the comment: ref #32911 And it's documented already. https://docs.python.org/3.7/whatsnew/3.7.html#changes-in-the-python-api -- nosy: +inada.naoki ___ Python tracker

[issue33477] Document that compile(code, 'exec') has different behavior in 3.7+

New submission from Matthias Bussonnier : In recent Python the following >>> from ast import PyCF_ONLY_AST >>> compile("'a'", 'whatever', 'exec', PyCF_ONLY_AST).body In 3.6 it return [<_ast.Expr at 0x10b7441d0>] # that contail Str('a') While on master: