[Mark Lutz] > So please: can we keep string around? Like it or not, we're > way past the point of removing such core modules at this point. Of course we're keeping string around. I already said that for backwards compatibility reasons it would not disappear before Py3K. I think there's a misunderstanding about the meaning of deprecation, too. That word doesn't mean to remove a feature. It doesn't even necessarily mean to warn every time a feature is used. It just means (to me) that at some point in the future the feature will change or disappear, there's a new and better way to do it, and that we encourage users to start using the new way, to save them from work later. In my mind, there's no reason to start emitting warnings about every deprecated feature. The warnings are only needed late in the deprecation cycle. PEP 5 says "There must be at least a one-year transition period between the release of the transitional version of Python and the release of the backwards incompatible version." Can we now stop getting all bent out of shape over this? String methods *are* recommended over equivalent string functions. Those string functions *are* already deprecated, in the informal sense (i.e. just that it is recommended to use string methods instead). This *should* (take notice, Fred!) be documented per 2.1. We won't however be issuing run-time warnings about the use of string functions until much later. (Lint-style tools may start warning sooner -- that's up to the author of the lint tool to decide.) Note that I believe Java makes a useful distinction that PEP 5 misses: it defines both deprecated features and obsolete features. *Deprecated* features are simply features for which a better alternative exists. *Obsolete* features are features that are only being kept around for backwards compatibility. Deprecated features may also be (and usually are) *obsolescent*, meaning they will become obsolete in the future. --Guido van Rossum (home page: http://www.python.org/~guido/)
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