Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upbpo-34605: Avoid master/slave terms #9101
Conversation
* Replace "master process" with "parent process" * Replace "master option mappings" with "main option mappings" * Replace "master pattern object" with "main pattern object" * ssl: replace "master" with "server" * And some other similar changes
vstinner
merged commit 5e92265
into
python:master
| @@ -223,7 +223,7 @@ def initialize_options(self): | |||
|
|
|||
| def finalize_options(self): | |||
| """Finalizes options.""" | |||
| # This method (and its pliant slaves, like 'finalize_unix()', | |||
| # This method (and its pliant childs, like 'finalize_unix()', | |||
ericvsmith
Sep 7, 2018
Member
I think this reads better as children. Although pliant isn't a very common word, and I'm not sure how it's being used here.
vstinner
Sep 7, 2018
Author
Member
Oh, maybe I should have waited longer before merging this one :-( I'm wasn't 100% sure between "childs" and "children". Sorry, english is not my first language. I created PR #9102 to replace childs with children.
I'm not sure what do you propose for pliant. In case of doubt, I leave it unchanged.
gvanrossum
Sep 11, 2018
Member
I Googled a bit and it seems "pliant slave" is an old-fashioned way to refer to slaves, and even more demeaning than just "slave" -- I presume it was meant ironically by the original author. We should really replace the entire construct "pliant slaves" with a more neutral term. I don't think "children" is the right term -- I propose "helpers".
* Replace "master process" with "parent process" * Replace "master option mappings" with "main option mappings" * Replace "master pattern object" with "main pattern object" * ssl: replace "master" with "server" * And some other similar changes
This comment was marked as disruptive content.
This comment was marked as disruptive content.
|
There is no point in continuing the debate. We’ve all had our say. If you
want to keep talking, go to Twitter.
On Tue, Sep 11, 2018 at 9:21 PM towerd ***@***.***> wrote:
In "Oxford Advanced Learners Dictionary", slave has an entry:
(specialist) a device that is directly controlled by another one
Words shall be interpreted in certain context. Otherwise, should every
word be interpreted literally? If one is named Cook, is he really a cook?
What's more, if slave can remind someone of bad things, shall every word
with some bad meaning be avoided? Stones can be related to weapon, sea can
drown people, shall these words be banned? The names of famous campus
killers, shall they be avoided to be used as names of new born babies,
because these names are used by killers'?
I'm afraid this seems like the "literary inquisition" that happened
numerous times in history. In those cases, word were interpreted in certain
ways deliberately, totally ignoring their context, and the related persons
were judged criminal just because they said those words.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#9101 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ACwrMiZ_OGkrJcqQ2ZHNZ4fklFjRyF3gks5uaIuzgaJpZM4WfAz6>
.
--
--Guido (mobile)
|
This comment was marked as disruptive content.
This comment was marked as disruptive content.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as disruptive content.
This comment was marked as disruptive content.
This comment was marked as disruptive content.
This comment was marked as disruptive content.
This comment was marked as disruptive content.
This comment was marked as disruptive content.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as disruptive content.
This comment was marked as disruptive content.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as disruptive content.
This comment was marked as disruptive content.
|
LGTM. Just few side comments. |
| @@ -72,7 +72,7 @@ class Verbose(Exception): | |||
| pass | |||
|
|
|||
| class Pattern: | |||
| # master pattern object. keeps track of global attributes | |||
| # main pattern object. keeps track of global attributes | |||
serhiy-storchaka
Sep 14, 2018
Member
Actually both wordings are wrong. This class doesn't represent a pattern object in any sense. I'll open a separate issue for this.
| @@ -1,7 +1,7 @@ | |||
| This directory contains a number of Python programs that are useful | |||
| while building or extending Python. | |||
|
|
|||
| buildbot Batchfiles for running on Windows buildslaves. | |||
serhiy-storchaka
Sep 14, 2018
Member
Interesting, "buildslave" was a term used in the Buildbot documentation: http://docs.buildbot.net/0.8.5/manual/cfg-buildslaves.html. In recent versions it was replaced with "worker": http://docs.buildbot.net/1.4.0/manual/cfg-workers.html.
In distutils.command.install, replace "pliant children" (previously, it was "pliant slaves") with "helpers". <!-- issue-number: [bpo-34605](https://www.bugs.python.org/issue34605) --> https://bugs.python.org/issue34605 <!-- /issue-number -->
https://bugs.python.org/issue34605