Message400788
> My use case for these low-level APIs is to write tests for low-level string/encoding handling in my custom use of the PyPreConfig and PyConfig structs. I wanted to verify that exact byte sequences were turned into specific representations inside of Python strings. This includes ensuring that certain byte sequences retain their appropriate "character" width in internal storage.
CPython contains many checks to ensure that a string always use the most effecient storage, especially in debug mode. The C API should not allow to create a string using an inefficient storage, unless you "abuse" the C API :-D
I'm not sure what do you test. |
|
Date |
User |
Action |
Args |
2021-08-31 22:02:29 | vstinner | set | recipients:
+ vstinner, georg.brandl, petr.viktorin, methane, serhiy.storchaka, indygreg |
2021-08-31 22:02:29 | vstinner | set | messageid: <1630447349.68.0.443293117091.issue45025@roundup.psfhosted.org> |
2021-08-31 22:02:29 | vstinner | link | issue45025 messages |
2021-08-31 22:02:29 | vstinner | create | |
|