A: Perhaps, they should have done less and the support would have been better. In the CPython reference implementation, the internal string representation was changed. The UTF-16 was replaced by one of three possible encodings (ISO-8859-1, UCS-2 or UCS-4) depending on the actual string content. To add a single non-ASCII or non-BMP character, the entire string will often be implicitly converted to a different encoding. The internal encoding is transparent to the script. This design is meant to optimize the performance of indexing operations on Unicode code points. However, we argue that counting or indexing code points should not be important for the majority of uses—compared, for instance, to grapheme clusters. To our knowledge, Python currently provides no support of the latter.
[14:28:35] us: "you may not upload, post or otherwise transmit any User Content that: (i) violates any law or engage in activity that would constitute a criminal offense or give rise to a civil liability; (ii) violates or infringes in any way upon the rights of others, including any intellectual property rights or make statements which may defame, harass, stalk or threaten others; (iii) is offensive in any fashion, including blatant expressions, racism, abusiveness, vulgarity, profanity, pornography, pedophilia, incest, bestiality, or otherwise obscene; (iv) advocates or provides instruction on illegal activity or discuss illegal activities or encourage illegal activity; (envy) is soliciting terrorism; (vi) contains advertising, promotional materials or any solicitation with respect to products or services; (vii) is not generally related to the designated topic or theme; (viii) contains software or other materials which contain a virus or other harmful or disruptive component;"