On Tue, Mar 24, 2020 at 11:55 AM Brett Cannon <brett@python.org> wrote:
-1 on "cut*" because my brain keeps reading it as "cute".
+1 on "trim*" as it is clear what's going on and no confusion with preexisting methods.
+1 on "remove*" for the same reasons as "trim*".

And if no consensus is reached in this thread for a name I would assume the SC is going to ultimately decide on the name if the PEP is accepted as the burden of being known as "the person who chose _those_ method names on str" is more than any one person should have bear. ;)

"raymondLuxuryYacht*" pronounced Throatwobbler Mangrove it is!
Never fear, the entire stdlib is full of naming inconsistencies and questionable choices accumulated over time.  Whatever is chosen will be lost in the noise and people will happily use it.

The original PEP mentioned that trim had a different use in PHP which is why I suggest avoiding that one.  I don't know how much crossover there actually is between PHP and Python programmers these days outside of FB.



Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-leave@python.org
Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/Z7TK4C5PPECBRTCTPKCJEABFM62TDYWW/
Code of Conduct: http://python.org/psf/codeofconduct/