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)
On Thu, Aug 6, 2009 at 14:01, Antoine Pitrou wrote:
>
> 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 hit
> 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?
There are always two dimensions in which to eval
Le vendredi 07 août 2009 à 00:02 +0200, "Martin v. Löwis" a écrit :
> There are always two dimensions in which to evaluate criticality of an
> issue: how serious is the problem it can cause when it hits, and in how
> many real applications is it likely to occur?
>
> In the first dimension, I agree
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 tell
On Thu, Aug 6, 2009 at 8:28 PM, Georg Brandl wrote:
> 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
On Thu, Aug 6, 2009 at 4:28 PM, Georg Brandl 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
On Thu, Aug 6, 2009 at 16:42, Guido van Rossum wrote:
> On Thu, Aug 6, 2009 at 4:28 PM, Georg Brandl 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
On Thu, Aug 6, 2009 at 5:42 PM, Brett Cannon wrote:
>
>
> On Thu, Aug 6, 2009 at 16:42, Guido van Rossum wrote:
>>
>> On Thu, Aug 6, 2009 at 4:28 PM, Georg Brandl wrote:
>> > Antoine Pitrou schrieb:
>> >> Hello,
>> >>
>> >> A data corruption issue has been discovered in the C IO lib in Python
>> >
On Thu, Aug 6, 2009 at 7:28 PM, Georg Brandl 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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Georg Brandl wrote:
>> 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
Hi everyone,
I'm just getting back from the nice trip to the Olympic Peninsula. I
should be able to do a release sometime next week. In the meantime,
could someone post the patch to the 3.1 download site? (We should add
a note to the quick links section, too.)
2009/8/6 Georg Brandl :
> We can eith
I have in the past done a microrelease without a release candidate. It
didn't go well.
On Fri, Aug 7, 2009 at 1:22 PM, Benjamin Peterson wrote:
> Hi everyone,
> I'm just getting back from the nice trip to the Olympic Peninsula. I
> should be able to do a release sometime next week. In the meanti
Benjamin Peterson schrieb:
> Hi everyone,
> I'm just getting back from the nice trip to the Olympic Peninsula. I
> should be able to do a release sometime next week.
Just at the right time! :)
> In the meantime,
> could someone post the patch to the 3.1 download site? (We should add
> a note to t
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.
Looking at Misc/NEWS, there are a number of worthy bugfixes already in.
Why not just do a regul
15 matches
Mail list logo
