<br><br><div class="gmail_quote">On Thu, Aug 6, 2009 at 16:42, Guido van Rossum <span dir="ltr"><<a href="mailto:guido@python.org">guido@python.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Thu, Aug 6, 2009 at 4:28 PM, Georg Brandl<<a href="mailto:g.brandl@gmx.net">g.brandl@gmx.net</a>> wrote:<br>
</div><div class="im">> Antoine Pitrou schrieb:<br>
>> Hello,<br>
>><br>
>> A data corruption issue has been discovered in the C IO lib in Python<br>
>> 3.1 (<a href="http://bugs.python.org/issue6629" target="_blank">http://bugs.python.org/issue6629</a>). I've applied a fix, and I wonder<br>
>> whether we should make a release quickly to minimize the probability of<br>
>> users hitting the problem?<br>
>> (Georg tells me Benjamin is on holiday, however)<br>
><br>
> FWIW, I also think we should make a new micro release right now. We can't<br>
> be seen to take data corruption issues with the most basic file operations<br>
> lightly, especially in Python 3; otherwise, people will think we still don't<br>
> consider it ready for use.<br>
><br>
> We can either make a release with only that patch applied, or a release of<br>
> the full 3.1-maint branch, but the latter would need alphas and betas.<br>
<br>
</div>+1</blockquote><div><br></div><div>Is that for the former or latter solution? Assuming the former, who is going to organize this since Benjamin is on vacation? And do we want just a source release or a full binary release (I assume the latter but the former is a lot easier)?</div>
<div><br></div><div>-Brett</div></div>