On Fri, Aug 6, 2021 at 12:23 PM Stephen J. Turnbull <turnbull.stephen.fw@u.tsukuba.ac.jp> wrote:
As a builtin, not my problem, I'm not the proponent. As a facility with *some* spelling, it's convenient in contexts where chr() is, but much less so (eg, coding ROT13 ;-). I know I've used this translation in mail hacking, but I don't recall whether the code was Python or Lisp.
Stephen does not advocate bchr() as a built-in or library function, but he just gave a great reason why it should not be a built-in: it's hard to find compelling and common use cases. A built-ins should be one or more of: - extremely useful in daily coding, like len() and list() etc. - foundational, like next(), classmethod() and iter() etc. - hard to create in Python code, like breakpoint(), compile() etc. super() is an example that fits all of those groups. bchr() (or whatever name it might have) fits none. Cheers, Luciano
Regards, Steve
_______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-leave@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/VBZBMCPQ... Code of Conduct: http://python.org/psf/codeofconduct/
-- Luciano Ramalho | Author of Fluent Python (O'Reilly, 2015) | http://shop.oreilly.com/product/0636920032519.do | Technical Principal at ThoughtWorks | Twitter: @ramalhoorg