This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author indygreg
Recipients georg.brandl, indygreg, methane, petr.viktorin, serhiy.storchaka, vstinner
Date 2021-08-30.16:38:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1630341534.57.0.645111343874.issue45025@roundup.psfhosted.org>
In-reply-to
Content
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.

I know there are alternative ways of performing this testing. But testing against the actual data structure used internally by CPython seemed the most precise since it isolates problems to the "store in Python" side of the problem and not "what does Python do once the data is stored."
History
Date User Action Args
2021-08-30 16:38:54indygregsetrecipients: + indygreg, georg.brandl, vstinner, petr.viktorin, methane, serhiy.storchaka
2021-08-30 16:38:54indygregsetmessageid: <1630341534.57.0.645111343874.issue45025@roundup.psfhosted.org>
2021-08-30 16:38:54indygreglinkissue45025 messages
2021-08-30 16:38:54indygregcreate