RetroSearch Browse

Tue Jul 7 14:41:37 CEST 2015 · https://mail.python.org/pipermail/python-dev/2015-July/140678.html

It's more complicated than that.

FWIW a crash reproducer doesn't mean it's a common or likely crash.
Apparently no unittests broke. Also, please give Raymond time to wake up
(I'm in Europe, but Raymond is probably recovering from a three-day weekend
in the US).

On Tue, Jul 7, 2015 at 2:32 PM, Maciej Fijalkowski <fijall at gmail.com> wrote:

> On Tue, Jul 7, 2015 at 2:14 PM, Guido van Rossum <guido at python.org> wrote:
> > FYI, do we have any indication that Raymond even read the comment? IIRC
> he
> > doesn't regularly read python-dev. I also don't think code review
> comments
> > ought to go to python-dev; the commiters list would seem more
> appropriate?
> > (Though it looks like python-checkins is configured to direct replies to
> > python-dev. Maybe we need to revisit that?)
>
> I kind of thought that python does pre-commit reviews (at least seems
> to apply to most people), so in case someone is completely exempt from
> that, maybe he should read python-dev or wherever the reply is set to?
> That also does not explain why a crashing commit has not been
> reverted.
>

-- 
--Guido van Rossum (python.org/~guido)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20150707/235f4344/attachment-0001.html>

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2015-July/140678.html below:

[Python-Dev] cpython: Tighten-up code in the set iterator to use an entry pointer rather than