2017-07-19 4:34 GMT+02:00 Nick Coghlan <ncogh...@gmail.com>: > 2. Indicate that it's a "lazily rendered" subclass that should hold > off on calling PyUnicode_Ready for as long as possible, but still do > so when necessary (akin to creating strings via the old Py_UNICODE > APIs and then calling PyUnicode_READY on them)
Py_UNICODE is deprecated and should go away in the long term. Serhiy Storchaka started to deprecate APIs using Py_UNICODE. We call PyUnicode_READY() *everywhere* to cast "legacy string" to the new compact format *as soon as possible*. So I don't think that you should abuse this machinery :-( Victor _______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
