CLN: Partially add future division imports
Adds division import to cases where something is already imported from **future** . #5445

It seems some trailing whitespace also got trimmed.
 this seems right but did anything fail?
 Passes locally (2.7.8), and Travis just came back green.
 what I mean is this doesn't make a difference 
why are we doing this?

maybe just close the issue?
 I haven't looked at all of the potentially-affected files (a quick, crude grep shows about 70 other files would need to be looked into). I was just trying to do something quick that would help with the referenced issue. No protests from me, if you would rather close. 
 my point is what does importing division do?
as everything is truediv at this point anyhow
what does it change? is it necessary?
 Ah. I did not know everything was truediv. In that case, probably best to close. My apologies.
 If you can produce a situation where this import actually changes things I think would be good to know. IIRC the purpose of this was to make the _tests_ always use true-div. can you reread the original issue and see. thxs
 @jtratner can you remind again what the necessity for importing `division` in each file is?
 not totally convinced this actually matters.
 It's not necessary, we fixed it to do true division where required ages ago
and now it would have zero impact.

On Thu, Mar 5, 2015 at 3:44 PM jreback notifications@github.com wrote:

> not totally convinced this actually matters.
> 
> —
> Reply to this email directly or view it on GitHub
> https://github.com/pydata/pandas/pull/8106#issuecomment-77477544.
