That's why I focused on pairs. I understand why some people might feel offended by the term slave (and master in opposition to it), despite personally feeling the concepts are detached. I never saw anyone oppose using the terms master/copy.

Trying to tie something as abstract and general as ugly/beautiful to body shaming is a considerably bigger stretch.

On Thu, 13 Sep 2018 at 14:22, Chris Angelico <rosuav@gmail.com> wrote:

On Thu, Sep 13, 2018 at 10:16 PM, João Santos <jmcs@jsantos.eu> wrote:
> One important difference between master/slave and beautiful/ugly is that the
> first pair are concrete concepts that typically applies to people, and the
> second are abstract concepts that always applied also to objects and
> abstract concepts.

You may or may not be right about "slave", but "master" is frequently
applied to objects - the document from which other copies are taken,
the template from which a cast is formed, etc. Even when applied to
people, it doesn't have to be paired with slavery - a "master" of a
skill is, well, someone who has mastered it. Excising the word master
from all documentation is likely impossible, and pointless.

And yes, I'm probably going to be slaughtered for saying this. But I
grew up around photocopiers, so to me, the "master" was the good
quality print-out that we stuck into the top of the copier, as opposed
to the "copies" that came out the front of it. Not everyone assumes
the worst about words.

ChrisA
_______________________________________________
Python-ideas mailing list
Python-ideas@python.org
https://mail.python.org/mailman/listinfo/python-ideas
Code of Conduct: http://python.org/psf/codeofconduct/