The Argument Clinic Derby is drawing to a close
The first release candidate of Python 3.4 will be tagged in about two weeks. We need to be completely done with the Derby by then. And it's going to take a while to review and iterate on the patches we've got. Therefore: I'm going to stop accepting submissions for new patches in two days. Patches posted to the issue tracker on or after Wednesday Jan 29 at 12:00:01am will not be accepted. If you have a patch you're still working on, you have until then to get it in. Please make sure that all patches, whether they've been posted yet or not, conform to the new conversion policy for the Derby: https://mail.python.org/pipermail/python-dev/2014-January/132066.html Thanks for participating! //arry/
On 01/26/2014 04:24 PM, Larry Hastings wrote:
Patches posted to the issue tracker on or after Wednesday Jan 29 at 12:00:01am will not be accepted.
Sorry, forgot to specify the time zone: PST, which is GMT -08:00. Put another way, the submission window closes about 55.5 hours from when I posted this message. Cheers, //arry/
On 2014-01-27 00:26, Larry Hastings wrote:
On 01/26/2014 04:24 PM, Larry Hastings wrote:
Patches posted to the issue tracker on or after Wednesday Jan 29 at 12:00:01am will not be accepted.
Sorry, forgot to specify the time zone: PST, which is GMT -08:00.
Put another way, the submission window closes about 55.5 hours from when I posted this message.
Put yet another way, 2014-01-29T08:00Z.
On 01/26/2014 04:24 PM, Larry Hastings wrote:
The first release candidate of Python 3.4 will be tagged in about two weeks. We need to be completely done with the Derby by then. And it's going to take a while to review and iterate on the patches we've got.
Since I was asked to clarify: we aren't going to convert every possible candidate function before the close of the Derby. We'll just ship what we have, and Python 3.4 will only have partial coverage for builtins. Once trunk reopens for Python 3.5 development work we'll pick up where we left off. Thanks again, //arry/
On Mon, Jan 27, 2014 at 2:24 AM, Larry Hastings <larry@hastings.org> wrote:
The first release candidate of Python 3.4 will be tagged in about two weeks. We need to be completely done with the Derby by then. And it's going to take a while to review and iterate on the patches we've got.
Therefore: I'm going to stop accepting submissions for new patches in two days. Patches posted to the issue tracker on or after Wednesday Jan 29 at 12:00:01am will not be accepted. If you have a patch you're still working on, you have until then to get it in.
Why not delay rc1 by a week or two and get this work done?
On 01/26/2014 08:07 PM, Tshepang Lekhonkhobe wrote:
On Mon, Jan 27, 2014 at 2:24 AM, Larry Hastings <larry@hastings.org> wrote:
The first release candidate of Python 3.4 will be tagged in about two weeks. We need to be completely done with the Derby by then. And it's going to take a while to review and iterate on the patches we've got.
Therefore: I'm going to stop accepting submissions for new patches in two days. Patches posted to the issue tracker on or after Wednesday Jan 29 at 12:00:01am will not be accepted. If you have a patch you're still working on, you have until then to get it in.
Why not delay rc1 by a week or two and get this work done?
We discussed that. The core developers, and Guido in particular, were against it. One good reason: if we slip Python 3.4 again we will miss shipping Python 3.4 final with Ubuntu 14.04. You can read the discussion in python-committers; it's under the subject "Status of the Derby, and request for another slip". https://mail.python.org/pipermail/python-committers/2014-January/002977.html //arry/
participants (3)
-
Larry Hastings -
MRAB -
Tshepang Lekhonkhobe