Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(91080)

Unified Diff: Lib/test/test_compile.py

Issue 16510: Using appropriate checks in tests
Patch Set: Created 5 years, 6 months ago
Use n/p to move between diff chunks; N/P to move between comments. Please Sign in to add in-line comments.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « Lib/test/test_compileall.py ('k') | Lib/test/test_complex.py » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
--- a/Lib/test/test_compile.py Fri Feb 07 17:53:13 2014 +0100
+++ b/Lib/test/test_compile.py Fri Feb 07 23:40:05 2014 +0200
@@ -422,7 +422,7 @@
for fname, code in sample_code:
co1 = compile(code, '%s1' % fname, 'exec')
ast = compile(code, '%s2' % fname, 'exec', _ast.PyCF_ONLY_AST)
- self.assertTrue(type(ast) == _ast.Module)
+ self.assertEqual(type(ast), _ast.Module)
co2 = compile(ast, '%s3' % fname, 'exec')
self.assertEqual(co1, co2)
# the code object's filename comes from the second compilation step
« no previous file with comments | « Lib/test/test_compileall.py ('k') | Lib/test/test_complex.py » ('j') | no next file with comments »

RSS Feeds Recent Issues | This issue
This is Rietveld 894c83f36cb7+