[issue4118] Built-in compile() and ast module doc issues

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Thanks for the suggestions! Changed in r67162. -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> _

[issue4118] Built-in compile() and ast module doc issues

Terry J. Reedy <[EMAIL PROTECTED]> added the comment: The 2.6 sentence that got deleted in 3.0: I at least somewhat agree. "When compiling a string with multi-line statements, two caveats apply: line endings must be represented by a single newline character ('\n'), and the input must be termina

[issue4118] Built-in compile() and ast module doc issues

Raymond Hettinger <[EMAIL PROTECTED]> added the comment: General comment: Stylistically, the docs should mostly be stated in a positive manner, stating what a tool does, how it should be used, and what is left undefined. IMO, it is harmful to fill the docs with CAVEATS and WARNINGS. --

[issue4118] Built-in compile() and ast module doc issues

Terry J. Reedy <[EMAIL PROTECTED]> added the comment: It appears that blanks on the last line also triggers a syntax error. See #4262. So the situation seems to be that the input must *sometimes* be terminated by . So adding 'sometimes' is the only change I would make, besides restoring th

[issue4118] Built-in compile() and ast module doc issues

New submission from Terry J. Reedy <[EMAIL PROTECTED]>: >From docs.python.org 2.6: Compile the source into a code or AST object. 3.0: Compile the source into a code object. Add 'or AST ' to the latter. Both: Refer to the _ast module documentation Both: for information on how to compile into an