[issue7432] Py3k doc: "from __future__ import division" not necessary

2010-01-05 Thread Ezio Melotti
Ezio Melotti added the comment: Fixed in r77314 (py3k) and r77315 (release31-maint), thanks! -- assignee: georg.brandl -> ezio.melotti resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker

[issue7432] Py3k doc: "from __future__ import division" not necessary

2009-12-07 Thread Ezio Melotti
Changes by Ezio Melotti : -- nosy: +ezio.melotti priority: -> normal ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscr

[issue7432] Py3k doc: "from __future__ import division" not necessary

2009-12-03 Thread Jared Grubb
Jared Grubb added the comment: Ditto on a few dozen lines later: INPLACE_TRUE_DIVIDE()¶ Implements in-place TOS = TOS1 / TOS when from __future__ import division is in effect. -- ___ Python tracker ___

[issue7432] Py3k doc: "from __future__ import division" not necessary

2009-12-03 Thread Jared Grubb
New submission from Jared Grubb : In the Python 3.1 docs for the 'dis' module, the following appears: ( http://docs.python.org/3.1/library/dis.html ) BINARY_TRUE_DIVIDE()¶ Implements TOS = TOS1 / TOS when from __future__ import division is in effect. There is always true in 3k, correct? The