> That said, I don't actually require that the code is written from > scratch. Instead, a detailed elaboration of how precisely the > implementation is approached, in the PEP, would be good. > > The PEP should also point out deficiencies of the approach taken, > e.g. the issue of spelling NaN, inf, etc. If it can be determined not > to be an issue in real life (i.e. for all interesting platforms), this > should be documented as well. I think that anything that might still be needed years after the code is adopted should be in comments in the code, not in a PEP. --Guido van Rossum (home page: http://www.python.org/~guido/)
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