GeezerVison

I have found a bug during testing. I'll extract it into a separate issue later.

I'll write the remaining tests after some rest.

I'll split it on three parts:

• higher-level C API corresponding to str methods
• lower-level C API
• codecs

I'll split it on three parts:

Are you talking about creating 3 PRs modifying the same files, or do you consider to have separated C and Python files for "higher-level C API corresponding to str methods"? Maybe it's just fine to put most "unicode" tests in "unicode.c" and "unicode.py" tests.

As you suggested, I'll add codecs tests in a separate Python file. The rest of tests will be in Lib/test/test_capi/test_unicode.py.

All wrappers will be defined in Modules/_testcapi/unicode.c. It is nice that it was separated from _testcapi.c.

• gh-99593: Add tests for Unicode C API (part 1) #99651
• gh-99593: Add tests for Unicode C API (part 2) #99868
• gh-99593: Add tests for Unicode C API (part 3) serhiy-storchaka/cpython#20

Since part 1 and 2 are merged, and part 3 (gh-104728) is in the queue, I recon we can close this :)