[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Python-Dev] Benchmarks why we need PEP 576/579/580

OK, I believe you, I was just referring to the relative irreproducibility
of Jeroen's results (see INADA Naoki's problems).

My main point is actually that until the Python core devs have elected a
new BDFL or come up with some other process for accepting PEPs, no action
will be taken on this PEP -- AFAIK there's no BDFL-Delegate for this PEP.
You can argue until you're blue in the face, but the new process won't be
ready until Jan 2019. (Read the python-committers archives, e.g.

To make this clear -- right now, there is no-one who can approve this PEP,
and you will have to wait until 2019 until there is.

Of course you can form a subcommittee where you try to agree on the
details, and I recommend that. But getting argumentative on python-dev is
not going to be very productive. In 2019 people will remember that you were
very forceful in taking your position, not what that position was or why
it's reasonable.

Sorry I don't have better news.

On Sun, Jul 22, 2018 at 5:52 AM, Stefan Behnel <stefan_ml at behnel.de> wrote:

> Guido van Rossum schrieb am 22.07.2018 um 01:14:
> > The cost would be if we were to end up maintaining all that code and it
> > wouldn?t make much difference.
> Well, this is exactly my point. Someone has to maintain the *existing* code
> base and help newcomers to get into it and understand it. This is not easy.
> The proposed implementation *already* makes a difference. And it does not
> even degrade the performance while doing that, isn't that great?
> To make this clear ? right now, there is someone who stands up and
> volunteers to invest the work to clean up the current implementation. He
> has already designed, and even implemented, a protocol that applies to all
> types of callables in the same way *and* that is extensible for current and
> future needs and optimisations. I think this is way more than anyone could
> ask for, and it would be very sad if this chance was wasted, and we would
> have to remain with the current implementation.
> Stefan
> _______________________________________________
> Python-Dev mailing list
> Python-Dev at python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe: https://mail.python.org/mailman/options/python-dev/
> guido%40python.org

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