[issue13677] correct docstring for builtin compile

Change by Serhiy Storchaka : -- versions: +Python 3.6, Python 3.7, Python 3.8 -Python 3.2, Python 3.3 ___ Python tracker ___ ___ Pyth

[issue13677] correct docstring for builtin compile

Éric Araujo added the comment: The compiler flags are not really documented in the ast module doc or anywhere: see #12207 and #1612012. -- ___ Python tracker ___ __

[issue13677] correct docstring for builtin compile

Changes by Éric Araujo : -- nosy: +eric.araujo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue13677] correct docstring for builtin compile

Terry J. Reedy added the comment: I am aware that the docstring, shown at help(compile), is what you were talking about. The docstring and manuals should say the same thing, or at least not contradict each other, so it is common for both to be out of date and both to be updated at the same ti

[issue13677] correct docstring for builtin compile

Jim Jewett added the comment: I'm not sure we're looking at the same thing. I was talking about the docstring that shows up at the interactive prompt in response to >>> help(compile) Going to hg.python.org/cpython and selecting branches, then default, then browse, got me to http://hg.python

[issue13677] correct docstring for builtin compile

Terry J. Reedy added the comment: Flags comment applies to 3.2.2 docs and 2.7.2 docs. There is only one additional flag: ast.PyCF_ONLY_AST, so 'flags' should be singular. As for src and dst, doc has been updated to say 'Compile the source into a code or AST object. ... source can either be a

[issue13677] correct docstring for builtin compile

New submission from Jim Jewett : The current docstring for compile suggests that the flags are strictly for selecting future statements. These are not the only flags. It also suggests that the source must be source code and the result will be bytecode, which isn't quite true. I suggest chang