> But with all due respect, there are already _lots_ of places in > Python that provide at least two ways to do something already. Exactly. My favourite one here is string exceptions, which have quite some analogy to the string module. At some time, there were only string exceptions. Then, instance exceptions were added, some releases later they were considered the better choice, so the standard library was converted to use them. Still, there is no sign whatsoever that anybody plans to deprecate string exceptions. I believe the string module will get less importance over time. Comparing it with string exception, that may be well 5 years. It seems there are two ways of "deprecation": a loud "we will remove that, change your code", and a silent "strings have methods" (i.e. don't mention the module when educating people). The latter approach requires educators to agree that the module is "uninteresting", and people to really not use once they find out it exists. I think deprecation should be only attempted once there is a clear sign that people don't use it massively for new code anymore. Removal should only occur if keeping the module less pain than maintaining it. 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