On Tue, 2003-12-30 at 22:23, Tim Peters wrote: > That's a big enough point that it deserves public airing, though: everyone > (except Guido, I guess) please remember what it was like when you first > learned Python! Mounds and mounds of library code written in Python, doing > interesting things with interesting techniques, and written at a high enough > level that you weren't wholly buried under details. Python's C code is > generally clean and educational too, but has a *much* smaller potential > audience than our pure-Python modules. Nobody can sanely accuse me of not > caring about speed (see a decade of speed-obsessed Python checkins for > counterexamples <wink>), but I cry a little each time a piece of the system > gets recoded in C. Keeping the original Python code around is a nice > compromise (pioneered, IIRC, by string.py, a loooong time ago). Yes, yes, yes. I'd be bummed if modules like pickle.py got lost or out of sync with its C cousin. -Barry
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