Paul Prescod wrote: > > "Eric S. Raymond" wrote: > > > > There has been a vast and echoing silence about the ascii.py module I > > posted here at Fred Drake's request. Is it really such a bad idea? > > Without looking closely, or even being particularly knowledgable (how's > that for a disclaimer!) my instinctive reaction was: "does the ASCII > subset of Unicode need its own module just before we add Unicode to the > language?" > > It may be that there are some semantics of ASCII that are not captured > in the Unicode spec. and thus are not generalizable. I'm pretty > confident that these ones ARE generalizable: > > isalnum > isalpha > isascii > islower > isupper > isspace > isxdigit > > How do Unicode users get this information from the famous Unicode > database and why not merge the Unicode and ASCII versions in 1.6? Note that many of the above are already implemented as string|Unicode methods. The Unicode database is accessible via the unicodedata module. The specs for the used APIs and constants can be found in the Unicode database description file on www.unicode.org. -- Marc-Andre Lemburg ______________________________________________________________________ Business: http://www.lemburg.com/ Python Pages: http://www.lemburg.com/python/
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