I proposed bytes.byte earlier in this thread: https://mail.python.org/archives/list/[email protected]/message/KBVVBJL2PHI55Y26Z4FMSCJPER242LFA/
Gregory dislikes the name: "I don't *like* to argue over names (the last stage of anything) but I do need to point out how that sounds to read". https://mail.python.org/archives/list/[email protected]/message/DGJWM3VMNMDBUTGYG72H5WLKDWBYFSUV/ That's why I proposed: bytes.fromchar(). I still like bytes.byte() :-) Victor On Thu, Sep 9, 2021 at 11:07 AM Antoine Pitrou <[email protected]> wrote: > > On Thu, 9 Sep 2021 18:55:04 +1000 > Nick Coghlan <[email protected]> wrote: > > > > P.S. The fact that it *didn't* look like the inverse operation for > > `int.from_bytes` was one advantage of calling the method > > `bytes.fromord` instead of `bytes.fromint`, but I'm still happy the SC > > is right that `bytes.fromint` is a more comprehensible method name > > overall. > > Perhaps we can call it `bytes.byte` to make it unambiguous? > > Regards > > Antoine. > > > _______________________________________________ > Python-Dev mailing list -- [email protected] > To unsubscribe send an email to [email protected] > https://mail.python.org/mailman3/lists/python-dev.python.org/ > Message archived at > https://mail.python.org/archives/list/[email protected]/message/WZUPBP4UASRCJLAKP6FMQJLLMYJY22CL/ > Code of Conduct: http://python.org/psf/codeofconduct/ -- Night gathers, and now my watch begins. It shall not end until my death. _______________________________________________ Python-Dev mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/6W4G32NOBXAQ73VESVE4UL7AZIWUAD6A/ Code of Conduct: http://python.org/psf/codeofconduct/
