[Python-bugs-list] [ python-Bugs-412436 ] compileall doesn't notice syntax errors
noreply@sourceforge.net
noreply@sourceforge.net
Tue, 17 Apr 2001 18:23:17 -0700
Bugs item #412436, was updated on 2001-03-30 02:59
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=412436&group_id=5470
Category: Python Library
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Jeremy Hylton (jhylton)
Summary: compileall doesn't notice syntax errors
Initial Comment:
compileall.py returns an exit code to indicate the
success or failure of compilation. This feature was
added in compileall.py revision 1.7 in response to
distutils message
http://mail.python.org/pipermail/distutils-sig/1999-March/000201.html
This is not as useful as it looks because a prior
change to py_compile.py (revision 1.13) catches syntax
errors, hiding them completely from compileall.py, so
compileall.py can't report the failure to its caller.
----------------------------------------------------------------------
>Comment By: Jeremy Hylton (jhylton)
Date: 2001-04-17 18:23
Message:
Logged In: YES
user_id=31392
Fixed in rev 1.9 of compileall.py. Note that this fix
causes a bunch of changes to the test suite, so that files
containing syntaxerrors are not compiled by compileall.
----------------------------------------------------------------------
Comment By: Jeremy Hylton (jhylton)
Date: 2001-04-13 14:16
Message:
Logged In: YES
user_id=31392
Will fix following the 2.1 release
----------------------------------------------------------------------
Comment By: Jeremy Hylton (jhylton)
Date: 2001-04-13 07:31
Message:
Logged In: YES
user_id=31392
I think this is easy enough to fix, but I don't know what
unintended side-effects the fix will have.
----------------------------------------------------------------------
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=412436&group_id=5470