RetroSearch Browse

Tue Jul 7 13:24:12 CEST 2015 · https://mail.python.org/pipermail/python-dev/2015-July/140671.html

On Tue, 7 Jul 2015 12:04:34 +0200
Maciej Fijalkowski <fijall at gmail.com> wrote:
> I must say I completely fail to understand the procedures under which
> python is developed. If the change (unreviewed, just randomly applied)
> causes crashes, then surely it should be reverted first and continued
> on bug tracker instead of lingering (and the complain sitting on bug
> tracker)?

+1, especially as the commit doesn't seem to come with any concrete
explanation of what is being fixed or improved.

("tighten-up code" is really a platonic motivation... not necessarily
bad, but should be trumped such as operational concerns, e.g.
crashes :-))

Regards

Antoine.

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

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

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