> One minor misgiving is that this call will *always* copy the string, > even if the internal coding of unicode objects is wchar_t. That's a > bit of a nuisance, but we can try to fix that later. Not sure what you mean by "later". Once this is being used, you cannot fix it anymore. Extensions *will* have to call PyMem_Free, and when they do so, changing the format specifier to do something better won't be possible, anymore, since the call to PyMem_Free will be in the way. Regards, Martin
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