Message224329
You were misinterpreting PEP 393 - it is only about the representation of string objects, and doesn't affect any pre-existing API. Changing Py_SetProgramName is not possible without breaking existing code, so it could only happen in Python 4.
A proper solution might be adding Py_SetProgramNameUTF8, but it could trick people into believing that argv[0] actually is UTF-8 on their system, which it might not be. Providing Py_SetProgramNameASCII might be better, but it could fail if argv[0] contains non-ASCII characters. Yet another solution could be to expose _Py_char2wchar to the developer.
In any case: yes, the example is outdated, and only valid for Python 2. |
|
Date |
User |
Action |
Args |
2014-07-30 17:47:53 | loewis | set | recipients:
+ loewis, vstinner, ezio.melotti, jj |
2014-07-30 17:47:53 | loewis | set | messageid: <1406742473.29.0.95851138422.issue22108@psf.upfronthosting.co.za> |
2014-07-30 17:47:53 | loewis | link | issue22108 messages |
2014-07-30 17:47:53 | loewis | create | |
|