Note: there's an patch available at http://python.org/sf/561928 Guido van Rossum wrote: > I think we can do two things. Either we can keep the docs for > deprecated features but clearly mark the chapter or section with a > deprecation note at the start, in bold. > > Or we can remove the docs for deprecated features, and add a chapter > "deprecated features" which mentions each deprecated feature without > describing it in detail, and provides information about what to use > instead. Either of these approaches works for me. > > The second idea, is to move responsibility for obsolesence warnings > > to PyChecker. > > This is not always feasible; some things can only be discovered at > run-time (e.g. the oct/hex/<< warnings). Agreed. PyChecker will probably just be an early warning system. Especially since I'm more aggressive on my definition of 'deprecated.' :-) Neal
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