[python-committers] Data corruption issue (C IO library)

[Guido van Rossum]

On Thu, Aug 6, 2009 at 5:42 PM, Brett Cannon<brett at python.org> wrote:
>
>
> On Thu, Aug 6, 2009 at 16:42, Guido van Rossum <guido at python.org> wrote:
>>
>> On Thu, Aug 6, 2009 at 4:28 PM, Georg Brandl<g.brandl at gmx.net> wrote:
>> > Antoine Pitrou schrieb:
>> >> Hello,
>> >>
>> >> A data corruption issue has been discovered in the C IO lib in Python
>> >> 3.1 (http://bugs.python.org/issue6629). I've applied a fix, and I
>> >> wonder
>> >> whether we should make a release quickly to minimize the probability of
>> >> users hitting the problem?
>> >> (Georg tells me Benjamin is on holiday, however)
>> >
>> > FWIW, I also think we should make a new micro release right now.  We
>> > can't
>> > be seen to take data corruption issues with the most basic file
>> > operations
>> > lightly, especially in Python 3; otherwise, people will think we still
>> > don't
>> > consider it ready for use.
>> >
>> > We can either make a release with only that patch applied, or a release
>> > of
>> > the full 3.1-maint branch, but the latter would need alphas and betas.
>>
>> +1
>
> 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)?

I just meant to +1 the "we need to make a new micro-release right now"
paragraph. Logistically, I think it needs to be a full binary release
but it could be identical to 3.1 except for the one patch. Hopefully
that obviates the need for alphas and betas. Who? Not me :-(

-- 
--Guido van Rossum (home page: http://www.python.org/~guido/)