A RetroSearch Logo

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

Search Query:

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

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

[Python-Dev] Benchmarks why we need PEP 576/579/580 [Python-Dev] Benchmarks why we need PEP 576/579/580Jeroen Demeyer J.Demeyer at UGent.be
Sun Jul 22 16:54:24 EDT 2018
On 2018-07-22 22:32, Antoine Pitrou wrote:
> Two things:
> - the issue26110 changes are not very large, it's just two additional
>    opcodes and a bit of support code

I didn't mean to compare PEP 580 to that specific issue, it was just an 
example. Even if issue26110 is small, the total complexity added by many 
incremental changes can still be big.

> - more importantly, issue26110 is entirely internal changes, while you
>    are proposing to add a new protocol (which is like a new API)

Just to make sure I understand you: your point is that it's 
automatically more complicated because it's an API instead of an 
internal change?
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4