Unless I'm missing something, part of M.-A. Lemburg's objection is: 1. The wchar_t type is itself an important interoperability story in C. (I'm not sure if this includes the ability, at compile time, to define wchar_t as either of two widths.)
2. The ability to work directly with wchar_t without a round-trip in/out of python format is an important feature that CPython has provided for C integrators. 3. The above support can be kept even without the wchar_t* member ... so saving the extra space on each string instance does not require dropping this support. -jJ _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/L3UWQN553EAR7KQSMG4KPI4PP3M6Y4ZX/ Code of Conduct: http://python.org/psf/codeofconduct/
