Re: Python 3 and PEP238 division

2008-03-18 Thread Ninereeds
On Mar 17, 7:26 pm, Terry Reedy [EMAIL PROTECTED] wrote: Ninereeds [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] | Is the PEP238 change to division going into Python 3 as planned? IDLE 3.0a3 1/2 0.5 | I realise that the new integer division semantics have been available | in

Re: Python 3 and PEP238 division

2008-03-18 Thread Marc 'BlackJack' Rintsch
On Tue, 18 Mar 2008 04:47:49 -0700, Ninereeds wrote: On Mar 17, 7:26 pm, Terry Reedy [EMAIL PROTECTED] wrote: 2.6, I have read, have optional 'Py3' warnings, and a 2to3 conversion program The tools can work out the *intent* of any particular division operator? Can work out whether the

Re: Python 3 and PEP238 division

2008-03-18 Thread Terry Reedy
Ninereeds [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] | On Mar 17, 7:26 pm, Terry Reedy [EMAIL PROTECTED] wrote: | Ninereeds [EMAIL PROTECTED] wrote in message | | news:[EMAIL PROTECTED] | | Is the PEP238 change to division going into Python 3 as planned? | | IDLE 3.0a3 1/2

Re: Python 3 and PEP238 division

2008-03-18 Thread Terry Reedy
Ninereeds [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] | On Mar 17, 7:26 pm, Terry Reedy [EMAIL PROTECTED] wrote: | Ninereeds [EMAIL PROTECTED] wrote in message | | news:[EMAIL PROTECTED] | | Is the PEP238 change to division going into Python 3 as planned? | | IDLE 3.0a3 1/2

Python 3 and PEP238 division

2008-03-17 Thread Ninereeds
Is the PEP238 change to division going into Python 3 as planned? I realise that the new integer division semantics have been available in from __future__ for quite a few years now, but a warning might be appropriate now that Python 3 is in alpha. A lot of people have probably either forgotten, or

Re: Python 3 and PEP238 division

2008-03-17 Thread Terry Reedy
Ninereeds [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] | Is the PEP238 change to division going into Python 3 as planned? IDLE 3.0a3 1/2 0.5 | I realise that the new integer division semantics have been available | in from __future__ for quite a few years now, but a warning might