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 eric.araujo
Recipients Oliver.Jeeves, dstufft, eric.araujo, tarek
Date 2014-03-18.02:52:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1395111156.12.0.421934946542.issue7918@psf.upfronthosting.co.za>
In-reply-to
Content
We all agree Python files with invalid syntax should be allowed, but some error message should be logged.  From the py_compile docs, this is already what the compile function does if the doraise argument is false (default), so what’s needed here is a unit test that makes sure we get a warning and the bad file is included in the sdist.

(I think we should not be concerned by the direct print to stderr instead of using proper logging: distutils uses its own logging system which lets one control the verbosity but does not have flexible filters, handlers and configuration, so in effect it’s like print to stderr.)
History
Date User Action Args
2014-03-18 02:52:36eric.araujosetrecipients: + eric.araujo, tarek, Oliver.Jeeves, dstufft
2014-03-18 02:52:36eric.araujosetmessageid: <1395111156.12.0.421934946542.issue7918@psf.upfronthosting.co.za>
2014-03-18 02:52:36eric.araujolinkissue7918 messages
2014-03-18 02:52:35eric.araujocreate