RE: [Zope] Future watch: how will python division change affectzo pe?

26 Jul 2001

      I think Guido is right in his idea that this should be integrated in 3.0+,
so this SHOULD NOT be that big of a deal.  That will keep it far off enough
that it will not have a severe impact.  I think fixing a design bug in the
language and just getting it done with is a good thing...  Integer division
operator // will be integrated into 2.2 to allow for us to start writing
good code premptively before 3.0...

Sean

-----Original Message-----
From: Farrell, Troy [mailto:troy.farrell@wcg.com]
Sent: Thursday, July 26, 2001 7:56 AM
To: 'zope@zope.org'
Subject: RE: [Zope] Future watch: how will python division change
affectzo pe?

I'm not sure about everyone's idea on this, but Backward Compatibility is a
Good Thing(tm).
Why don't we just say:
1/2  == 0
1//2 == 0.5

Troy

-----Original Message-----
From: Steve Drees [mailto:drees@the-bridge.net]
Sent: Thursday, July 26, 2001 8:56 AM
To: Dieter Maurer; Chris Withers
Cc: marc lindahl; zope@zope.org
Subject: RE: [Zope] Future watch: how will python division change
affectzope?
...
Chris Withers writes:
...
marc lindahl wrote:
...
To me this sounds like a huge mistake -- it's a different
escalation rule
...
than any other language.
Go to agree with that. What are the reasons _for_ doing this?
Most people without knowledge of "C" derived programming languages
are astonished that "1/2" can be "0".
Marc & Chris are wrong here. Every 3rd grader in the US knows that 1/2 is
not 0.
So I would say that (american) english agrees with the proposed new division
rules in python.

_______________________________________________
Zope maillist  -  Zope@zope.org
http://lists.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope-dev )

RE: [Zope] Future watch: how will python division change affectzo pe?

sean.upton＠uniontrib.com