Raymond Hettinger wrote: > One other thought: In deciding how long to leave module in, we should > consider that Python books are updated infrequently, if at all. It > would be a bummer if code in them stopped working as advertised. Correct. Thanks for reminding me - that is indeed a reasoning that is typically brought up by book authors, so I should have brought it up myself :-) Of course, developers would first see the deprecation warning, which would tell them that their books are outdated. However, if the code is removed, they get an import error, which leaves them guessing what the problem might have been. Regards, Martin
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