@SRAZKVT it's both better and worse than that. it specifically uses the STRINGLIB_CHAR macro but redefines it in source files that deal with bytes to be a char
Post
@SRAZKVT in ucs4lib.h (i think that's utf-32 right?) it has #define STRINGLIB_CHAR Py_UCS4
@SRAZKVT making bytes vs string safer was always a completely made up excuse for the 2->3 move. people in the community genuinely think breaking changes are a moral good
@hipsterelectron breaking changes are good when they're necessary
when they're not, please don't
