checks: do not run pyflake on removed file
authorPierre-Yves David <pierre-yves.david@ens-lyon.org>
Tue, 14 Mar 2017 14:19:11 -0700
changeset 2107 42f3329aa144
parent 2102 e243e1d9464c
child 2108 206066375dcb
checks: do not run pyflake on removed file The fileset matches removed files. This confuses pyflakes for good reasons.
tests/test-check-pyflakes.t
--- a/tests/test-check-pyflakes.t	Tue Mar 14 11:26:55 2017 -0700
+++ b/tests/test-check-pyflakes.t	Tue Mar 14 14:19:11 2017 -0700
@@ -7,5 +7,5 @@
 run pyflakes on all tracked files ending in .py or without a file ending
 (skipping binary file random-seed)
 
-  $ hg locate 'set:**.py or grep("^!#.*python")' 2>/dev/null \
-  > | xargs pyflakes 2>/dev/null  
+  $ hg locate 'set:(**.py or grep("^!#.*python")) - removed()' 2>/dev/null \
+  > | xargs pyflakes 2>/dev/null