Skip Montanaro <skip@pobox.com> writes: > How about deprecating the string module? In the past, this has presented > two major problems. First, its near ubiquity in Python programs before the > availability of string methods. Second, the presence of a few useful data > objects (digits, uppercase, etc). The first problem can be solved by > extending the deprecation time suitably (two years/four releases?) I think > the second problem can be solved by adding those data objects to either sys > or locale(preferably the latter). I think one needs to offer the alternatives first, and deprecate the module then. So have alternatives for *everything* in string available in 2.3, deprecate it in 2.4, add a DeprecationWarning in 2.5. 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