<br><br><div><span class="gmail_quote">On 5/29/06, <b class="gmail_sendername">Bob Ippolito</b> <<a href="mailto:bob@redivi.com">bob@redivi.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>A compromise is to do proper range checking as a warning, and do the modulo math anyway... but is that what we really want?</div></blockquote><div><br>I don't know about the rest of 'us', but that's what I want, yes: backward compatibility, and a warning to tell people to fix their code 'or else'. The prevalence of the warnings (outside of the stdlib) should give us a clue whether to make it an exception in
2.6 or wait for 2.7/3.0.<br></div></div><br>Perhaps more people could chime in? Am I being too anal about backward compatibility here?<br><br>-- <br>Thomas Wouters <<a href="mailto:thomas@python.org">thomas@python.org</a>
><br><br>Hi! I'm a .signature virus! copy me into your .signature file to help me spread!