On Sat, Mar 21, 2020 at 11:35 AM Steven D'Aprano <st...@pearwood.info> 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 > > <sweeney.dennis...@gmail.com> 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.
Whereas they don't have to teach "start" and "end", because kids already know them before they start 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? Yeah. Jargon is fine when there's no regular word with appropriate precision, but we shouldn't use jargon just for jargon's sake. Python has a long tradition of preferring regular words when possible, e.g. using not/and/or instead of !/&&/||, and startswith/endswith instead of hasprefix/hassuffix. -n -- Nathaniel J. Smith -- https://vorpus.org _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@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/SMZB6KII42ZSLOFJGDMFRXXPM72UGQ3D/ Code of Conduct: http://python.org/psf/codeofconduct/
