On Fri, 28 Jan 2011 20:05:30 -0500, Steve Holden wrote:
> Antoine is quite correct. The strict process would be to include a note it
> the NEWS file pointing out that this deficiency was found too late for the
> necessary fixes to be applied in a controlled manner.
I think a warning in the docume
On Jan 29, 2011, at 12:04 AM, R. David Murray wrote:
> If the module weren't already broken for most real-world purposes I'd
> no question want to wait. As it is I'm on the fence.
Me too, but I did want to acknowledge the correctness of Antoine's argument.
Yes, I reminded people (using multipr
Antoine is quite correct. The strict process would be to include a note it the
NEWS file pointing out that this deficiency was found too late for the
necessary fixes to be applied in a controlled manner.
I was not thinking straight: I remember arguing in the past that
multiprocessing should be
While I agree the mailbox module is basically useless right now, the
fact that we are using the rc phase for common bug fixing means the rc
phase has become useless too. That may become a quality problem in the
middle term. On the other hand, if the RM refused all non-trivial
patches during the rc
On Jan 28, 2011, at 12:35 PM, Steve Holden wrote:
> As teh reporter of that bug I should like to say in Victor's, Antoine's and
> David's support that the module is so broken without this patch that the
> module should not really have been included in a production release.
>
> Even if the curr
As teh reporter of that bug I should like to say in Victor's, Antoine's and
David's support that the module is so broken without this patch that the module
should not really have been included in a production release.
Even if the current patch is broken, I believe the results of using that code
Hi,
Le vendredi 28 janvier 2011 à 12:06 +0100, Georg Brandl a écrit :
> this is just a heads-up that I'll be freezing py3k for the rc2 release
> in a bit less than 48 hours -- Sunday morning in CET.
>
> Please get all changes that you already know are necessary reviewed and
> committed *before* t
Hi guys,
this is just a heads-up that I'll be freezing py3k for the rc2 release
in a bit less than 48 hours -- Sunday morning in CET.
Please get all changes that you already know are necessary reviewed and
committed *before* that: the goal is zero commits between rc2 and final
(although I know it
