[Python-Dev] Benchmarks why we need PEP 576/579/580
Stefan Behnel
stefan_ml at behnel.de
Sun Jul 22 17:09:05 EDT 2018
More information about the Python-Dev mailing list
Sun Jul 22 17:09:05 EDT 2018
- Previous message (by thread): [Python-Dev] Benchmarks why we need PEP 576/579/580
- Next message (by thread): [Python-Dev] Benchmarks why we need PEP 576/579/580
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jeroen Demeyer schrieb am 22.07.2018 um 22:54: > On 2018-07-22 22:32, Antoine Pitrou wrote: >> - 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? I think it's more that it changes something substantial in a way that is not just internal but visible to users. I think it's more than just a tracker issue and worth going through the PEP process. Stefan
- Previous message (by thread): [Python-Dev] Benchmarks why we need PEP 576/579/580
- Next message (by thread): [Python-Dev] Benchmarks why we need PEP 576/579/580
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list