Reflect Antoine's comments.
This commit is contained in:
parent
6ec6d73ccd
commit
f30420c210
|
@ -213,11 +213,16 @@ Several concerns have been raised about the approach presented here:
|
|||
It makes the implementation more complex. That's true, but considered
|
||||
worth it given the benefits.
|
||||
|
||||
The Py_Unicode representation is not instantaneously available,
|
||||
The Py_UNICODE representation is not instantaneously available,
|
||||
slowing down applications that request it. While this is also true,
|
||||
applications that care about this problem can be rewritten to use the
|
||||
str representation.
|
||||
|
||||
The question was raised whether the wchar_t representation is
|
||||
discouraged, or scheduled for removal. This is not the intent of this
|
||||
PEP; applications that use them will see a performance penalty,
|
||||
though. Future versions of Python may consider to remove them.
|
||||
|
||||
Copyright
|
||||
=========
|
||||
|
||||
|
|
Loading…
Reference in New Issue