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. --- doc/numpybook/runcode.py | 31 +++++++++++++++++-------------- 1 file changed, 17 insertions(+), 14 deletions(-) (limited to 'doc/numpybook/runcode.py') diff --git a/doc/numpybook/runcode.py b/doc/numpybook/runcode.py index 7ec303500..92784d34e 100644 --- a/doc/numpybook/runcode.py +++ b/doc/numpybook/runcode.py @@ -1,17 +1,20 @@ -# This script takes a lyx file and runs the python code in it. -# Then rewrites the lyx file again. -# -# Each section of code portion is assumed to be in the same namespace -# where a from numpy import * has been applied -# -# If a PYNEW inside a Note is encountered, the name space is restarted -# -# The output (if any) is replaced in the file -# by the output produced during the code run. -# -# Options: -# -n name of code section (default MyCode) -# +""" +This script takes a lyx file and runs the python code in it. + Then rewrites the lyx file again. + +Each section of code portion is assumed to be in the same namespace +where a from numpy import * has been applied + + If a PYNEW inside a Note is encountered, the name space is restarted + +The output (if any) is replaced in the file + by the output produced during the code run. + +Options: + -n name of code section (default MyCode) + +""" +from __future__ import division import sys import optparse -- cgit v1.2.1