On 9/5/2017 10:40 AM, Guido van Rossum wrote: > On Tue, Sep 5, 2017 at 5:58 AM, Simon Cross > <hodgestar+pythondev at gmail.com <mailto:hodgestar+pythondev at gmail.com>> > wrote: > > I thought the decision a few years ago was that all modules that > have a C library for performance reasons should also have a Python > version? Did this decision change at some point? (just curious). > > It was never meant as a hard rule. IIRC the actual rule is more that > *if* you have both a C and a Python version they need to supply the same > API, *and* the naming should be e.g. _pickle (C) and pickle (Python), > *and* the Python version should automatically replace itself with the C > version when the latter exists (e.g. by putting an import * at the end > with a try/except around it). *And* both versions should be tested in the test file ;-). -- Terry Jan Reedy
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