Steven D'Aprano wrote: > - If it is no burden to have to import a module and call an external > function for some transformations, why have encode and decode methods at > all? Now that all text strings are unicode, the unicode codecs are in a sense special, in that you can't do any string I/O at all without using them at some stage. So arguably it makes sense to have a very easy way of invoking them. I suspect that without this, the idea of all strings being unicode would have been even harder to sell than it was. -- Greg
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