holger krekel writes: > But isn't this a case where the number of people who *will* use > it in the future exceeds the current number of users by a factor > of 10 or 100? Hopefully! > Is it really worth the possible confusion? The suggestion wasn't that we document the old names as deprecated, but to simply not document them. Only people with existing code using the package will be using them. We certainly could add a DeprecationWarning for the warn() method. > Introducing a new module with already "deprecated" method names > seems strange to me. The catch, of course, is that we're not introducing it, we're simply adding it to the standard library. -Fred -- Fred L. Drake, Jr. <fdrake at acm.org> PythonLabs at Zope Corporation
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