Thomas Wouters writes: > FWIW, I agree that in time, the string module should be deprecated. But I > also think that 'in time' should be a considerable timespan. Don't deprecate *If* most functions in the string module are going to be deprecated, that should be done *now*, so that the documentation will include the appropriate warning to users. When they should actually be removed is another matter, and I think Guido is sufficiently aware of their widespread use and won't remove them too quickly -- his creation of Python isn't the reason he's *accepted* as BDFL, it just made it a possibility. He's had to actually *earn* the BDFL position, I think. With regard to converting the standard library to string methods: that needs to be done as part of the deprecation. The code in the library is commonly used as example code, and should be good example code wherever possible. > support old code. And don't forget to document it 'deprecated' everywhere, > not just one minor release note. When Guido tells me exactly what is deprecated, the documentation will be updated with proper deprecation notices in the appropriate places. -Fred -- Fred L. Drake, Jr. <fdrake at acm.org> PythonLabs at Digital Creations
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