On 7/11/06, <b class="gmail_sendername"><a href="mailto:skip@pobox.com">skip@pobox.com</a></b> <<a href="mailto:skip@pobox.com">skip@pobox.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Brett> That whole entry is a little overblown.<br><br>Well, sure. Think of it as a bug report with attitude. ;-)<br><br> Brett> That was done to fix buffer overflow issues when libc<br> Brett> implementations didn't do bound checks on the arguments to
<br> Brett> strftime() and would index too far...<br><br>That special case could simply be recognized and converted into one that<br>works couldn't it? Documented or not, I believe it was the standard idiom<br>for formatting just a date before
2.4.<br><br> <a href="http://python.org/sf/1520914">http://python.org/sf/1520914</a><br><br>Keep or toss as you see fit. Seems like breakage that could have been<br>avoided to me though.</blockquote><div><br>Right, but that would have required realizing how to prevent it at the time. =)
<br><br>I can change it so that 0 is an acceptable value and internally handles defaulting to something reasonable (accepting less than 9 values in the tuple is a separate thing that I don't feel like bothering to implement). It does possibly hide bugs where 0 was not meant to be passed, though.
<br><br>If people think this is a reasonable thing to change, then Neal and Anthony, do you want it to go into 2.5?<br><br>-Brett<br></div></div>