> Because I want to reserve the right to change the semantics > *inside* unicodeobject.c at some later point. Note that currently > no caching of Unicode objects takes place, but this could change > in the future and indeed your patch starts into this direction. So would you accept a patch that corrects all calls to PyUnicode_FromUnicode which modify the result they get, without having passed a NULL str argument? 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