This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Jim.Jewett
Recipients Jim.Jewett, docs@python
Date 2011-12-29.17:49:21
SpamBayes Score 0.0007611477
Marked as misclassified No
Message-id <1325180963.04.0.479072583529.issue13677@psf.upfronthosting.co.za>
In-reply-to
Content
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 changing:

"The flags argument, if present, controls which future statements influence the compilation of the code."

to:

"The flags argument, if present, largely controls which future 
statements influence the compilation of the code.  (Additional 
flags are documented in the AST module.)"
History
Date User Action Args
2011-12-29 17:49:23Jim.Jewettsetrecipients: + Jim.Jewett, docs@python
2011-12-29 17:49:23Jim.Jewettsetmessageid: <1325180963.04.0.479072583529.issue13677@psf.upfronthosting.co.za>
2011-12-29 17:49:22Jim.Jewettlinkissue13677 messages
2011-12-29 17:49:22Jim.Jewettcreate