<br><br><div><span class="gmail_quote">On 3/14/07, <b class="gmail_sendername">Steven Bethard</b> <<a href="mailto:firstname.lastname@example.org">email@example.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;">
On 3/14/07, Thomas Wouters <<a href="mailto:firstname.lastname@example.org">email@example.com</a>> wrote:<br>><br>><br>> On 3/14/07, Raymond Hettinger <<a href="mailto:firstname.lastname@example.org">email@example.com</a>> wrote:<br>
> > - In 3.0, we don't want an exception.<br>><br>> Eh, no, you might not want one, but I most assuredly do want an exception.<br>> Having formerly-octal literals suddenly give wrong results would be much
<br>> more of a stumbling block than having them in the first place, especially<br>> considering we forgot to change all the other languages out there. An<br>> exception can make the difference between '0t60' and '60' clear in a single
<br>> message, not to mention refuse the temptation to guess.<br><br>Sorry, but could you explain why having the -py3k flag raise the<br>exception for your 2.X code wouldn't be sufficient? Is it because you<br>expect your fingers will continue to type 0660 instead of 0t660 when
<br>you're writing Python 3000 code?</blockquote><div><br>Not just me. The world. This isn't a "re-educate people used to a wart in Python 2.x" kind of thing. This is a "re-educate new programmers coming from other languages" kind of thing. The stuff we warn about with -Wpy3k in Python
2.6 is stuff that is a change in how Python 3.0 does things compared to 2.x. This isn't just a change compared to 2.6, this is a change compared to quite a lot of popular programming languages out there.<br></div></div>
<br>-- <br>Thomas Wouters <<a href="mailto:firstname.lastname@example.org">email@example.com</a>><br><br>Hi! I'm a .signature virus! copy me into your .signature file to help me spread!