| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
PEP-387 says (and did say back when these types were deprecated in 3.13): > If the expected maintenance overhead and security risk of the > deprecated behavior is small (e.g. an old function is > reimplemented in terms of a new, more general one), > it can stay indefinitely (or until the situation changes). There's no need to remove these.
Documentation build overview6 files changed · ± 6 modified ± Modified |
Sorry, something went wrong.
There was a problem hiding this comment.
Py_UNICODE and Py_UNICODE_TYPE are legacy of Python 3.2 which had this annoying "narrow vs wide" build. Python 3.3 and newer now uses Py_UCS4 which is 32-bit on all platforms. I don't think that we should keep them longer. It doesn't seem to be a big deal to remove these types: #154759 (comment).
If you want wchar_t, well, use wchar_t. Don't use Py_UNICODE or Py_UNICODE_TYPE.
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
PEP-387 says (and did say back when these types were deprecated in 3.13):
There's no need to remove two one-line typedefs.