From 6aa264c4bad9c89ccdd9ecd5a1cb5ef10643ec51 Mon Sep 17 00:00:00 2001 From: Charles Harris Date: Wed, 27 Feb 2013 13:26:58 -0700 Subject: 2to3: Put `from __future__ import division in every python file. This should be harmless, as we already are division clean. However, placement of this import takes some care. In the future a script can be used to append new features without worry, at least until such time as it exceeds a single line. Having that ability will make it easier to deal with absolute imports and printing updates. --- tools/c_coverage/c_coverage_report.py | 2 ++ 1 file changed, 2 insertions(+) (limited to 'tools/c_coverage/c_coverage_report.py') diff --git a/tools/c_coverage/c_coverage_report.py b/tools/c_coverage/c_coverage_report.py index 0c9574511..48f1eb8dc 100755 --- a/tools/c_coverage/c_coverage_report.py +++ b/tools/c_coverage/c_coverage_report.py @@ -2,7 +2,9 @@ """ A script to create C code-coverage reports based on the output of valgrind's callgrind tool. + """ +from __future__ import division import optparse import os -- cgit v1.2.1