mbiggs added the comment: So a correct statement would be "A UTF-8 string is turned into a sequence of bytes that contains embedded zero bytes only where they represent the NULL character (U+0000)." I think it's important to correct this because the part about processing UTF-8 with C functions like strcpy(), was wrong and could cause bugs. ---------- _______________________________________ Python tracker https://bugs.python.org/issue36789 _______________________________________

Josh Rosenberg added the comment: Minor bikeshed: If updating the documentation, refer to U+0000 as "the null character" or "NUL", not "NULL". Using "NULL" allows for confusion with NULL pointers; "the null character" (the name used in the Unicode standard) or "NUL" (the official three letter abbreviation in ASCII, Unicode too I think) has no such opportunity for confusion. ---------- nosy: +josh.r _______________________________________ Python tracker https://bugs.python.org/issue36789 _______________________________________

Change by redshiftzero : ---------- keywords: +patch pull_requests: +13026 stage: needs patch -> patch review _______________________________________ Python tracker https://bugs.python.org/issue36789 _______________________________________

mbiggs added the comment: Ah sent a pull request but didn't realize that redshiftzero already had. Their PR looks good to me. Thanks for fixing this! ---------- _______________________________________ Python tracker https://bugs.python.org/issue36789 _______________________________________

Change by Cheryl Sabella : ---------- resolution: -> fixed stage: patch review -> resolved status: open -> closed _______________________________________ Python tracker https://bugs.python.org/issue36789 _______________________________________