Brian Curtin added the comment:
This went over a year without a request to undo it, and we've since made
several releases that includes it, so I'm closing this. Please re-open if it
does need to be reverted.
--
status: open - closed
___
Python
New submission from Robert Xiao nneon...@gmail.com:
Lib/random.py in Python 3.2 contains the line
from __future__ import division
even though it is no longer necessary, as true float division is the default in
Python 3.
Trivial patch:
--- lib/python3.2/random.py 2011-09-03
Roundup Robot devn...@psf.upfronthosting.co.za added the comment:
New changeset 3fdc5a75d6e1 by Brian Curtin in branch '3.2':
Fix #13384. Remove __future__ import in 3.x code.
http://hg.python.org/cpython/rev/3fdc5a75d6e1
--
nosy: +python-dev
___
Changes by Brian Curtin br...@python.org:
--
assignee: - brian.curtin
nosy: +brian.curtin
resolution: - fixed
stage: - committed/rejected
status: open - closed
type: - behavior
versions: -Python 3.4
___
Python tracker rep...@bugs.python.org
Raymond Hettinger raymond.hettin...@gmail.com added the comment:
I thought we had a policy that future imports would never be removed.
--
nosy: +rhettinger
status: closed - open
___
Python tracker rep...@bugs.python.org
Brian Curtin br...@python.org added the comment:
That's news to me since it probably pre-dates my involvement around here. I'll
revert if that's correct.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13384
Benjamin Peterson benja...@python.org added the comment:
Things won't ever be removed from the __future__ module, but there's no harm in
removing ones with no effect.
--
nosy: +benjamin.peterson
___
Python tracker rep...@bugs.python.org
Raymond Hettinger raymond.hettin...@gmail.com added the comment:
At one point, for 2.x at least, we weren't removing the from __future__
imports even after the feature became available.
--
___
Python tracker rep...@bugs.python.org
Ezio Melotti ezio.melo...@gmail.com added the comment:
AFAIK on 2.x there are a few modules that are supposed to work even with older
version of Python (I think I even saw one that is supposed to still be
compatible with Python 1.5).
I don't think this is the case for Python 3 though.
