summaryrefslogtreecommitdiff
path: root/numpy/dual.py
diff options
context:
space:
mode:
authorCharles Harris <charlesr.harris@gmail.com>2013-02-27 13:26:58 -0700
committerCharles Harris <charlesr.harris@gmail.com>2013-03-01 11:22:47 -0700
commit6aa264c4bad9c89ccdd9ecd5a1cb5ef10643ec51 (patch)
tree15cad18dacf1ef03380c957ed9af4f39b94c5012 /numpy/dual.py
parent3c13c0a925276130d66be490eed4ae337712cce2 (diff)
downloadnumpy-6aa264c4bad9c89ccdd9ecd5a1cb5ef10643ec51.tar.gz
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.
Diffstat (limited to 'numpy/dual.py')
-rw-r--r--numpy/dual.py2
1 files changed, 2 insertions, 0 deletions
diff --git a/numpy/dual.py b/numpy/dual.py
index 4aa01cd30..15b175b92 100644
--- a/numpy/dual.py
+++ b/numpy/dual.py
@@ -10,6 +10,8 @@ Numpy.
.. _Scipy : http://www.scipy.org
"""
+from __future__ import division
+
# This module should be used for functions both in numpy and scipy if
# you want to use the numpy version if available but the scipy version
# otherwise.