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 brett.cannon
Recipients brett.cannon, eric.araujo, proski, r.david.murray, terry.reedy
Date 2015-10-09.19:52:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
You can verify a script is syntactically correct by compiling it to an AST or just calling compile() which is another way of doing essentially what `import` does but without having to worry about import-related side-effects in the code being checked.

But is this really worth adding to the stdlib? You can run your tests to verify the code is syntactically sound, run pylint, etc. I think this is probably straying a bit too much into the tooling arena to make the maintenance burden worth having in the stdlib.
Date User Action Args
2015-10-09 19:52:59brett.cannonsetrecipients: + brett.cannon, terry.reedy, eric.araujo, r.david.murray, proski
2015-10-09 19:52:59brett.cannonsetmessageid: <>
2015-10-09 19:52:59brett.cannonlinkissue25303 messages
2015-10-09 19:52:59brett.cannoncreate