>> BTW, a sane collection of typedefs would be another good candidate for >> pyport.h. [M.-A. Lemburg] > Good idea. > > The only problem with typedefs is that they tend to cause conflicts > when different definitions are encountered. > We'd have to use e.g. Py_UINT4, Py_UINT2, etc... Yes, but that's a hell of a lot better than the path the patch in question started going down, w/ its Unicode-specific _PyUnicode_Int32 and (! probably a bug) _PyUNICODE_Int32.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4