[python-committers] Data corruption issue (C IO library)
brett at python.org
Fri Aug 7 02:42:35 CEST 2009
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
> >> 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
> > be seen to take data corruption issues with the most basic file
> > lightly, especially in Python 3; otherwise, people will think we still
> > consider it ready for use.
> > We can either make a release with only that patch applied, or a release
> > the full 3.1-maint branch, but the latter would need alphas and betas.
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
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the python-committers