On Sun, Mar 22, 2020 at 5:41 AM Steven D'Aprano <[email protected]> wrote: > > On Fri, Mar 20, 2020 at 06:18:20PM -0700, Nathaniel Smith wrote: > > On Fri, Mar 20, 2020 at 11:54 AM Dennis Sweeney > > <[email protected]> wrote: > > > This is a proposal to add two new methods, ``cutprefix`` and > > > ``cutsuffix``, to the APIs of Python's various string objects. > > > > The names should use "start" and "end" instead of "prefix" and > > "suffix", to reduce the jargon factor > > Prefix and suffix aren't jargon. They teach those words to kids in > primary school. > > Why the concern over "jargon"? We happily talk about exception, > metaclass, thread, process, CPU, gigabyte, async, ethernet, socket, > hexadecimal, iterator, class, instance, HTTP, boolean, etc without > blinking, but you're shying at prefix and suffix? >
As a general rule, jargon from your OWN domain is easier to justify than jargon from some OTHER domain. (Though in this case, I agree that "prefix" and "suffix" shouldn't be a problem.) ChrisA _______________________________________________ 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/BSCTUBWDBFHOJQJKBX2HFTDSWHI6VGCV/ Code of Conduct: http://python.org/psf/codeofconduct/
