> As you may have noticed, the Unicode objects provide > new methods .islower(), .isupper() and .istitle(). Finn Bock > mentioned that Java also provides .isdigit() and .isspace(). > > Question: should Unicode also provide these character > property methods: .isdigit(), .isnumeric(), .isdecimal() > and .isspace() ? Plus maybe .digit(), .numeric() and > .decimal() for the corresponding decoding ? What would be the difference between isdigit, isnumeric, isdecimal? I'd say don't do more than Java. I don't understand what the "corresponding decoding" refers to. What would "3".decimal() return? > Similar APIs are already available through the unicodedata > module, but could easily be moved to the Unicode object > (they cause the builtin interpreter to grow a bit in size > due to the new mapping tables). > > BTW, string.atoi et al. are currently not mapped to > string methods... should they be ? They are mapped to int() c.s. --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