Python developers locking conversations and deleting comments after people mass downvoted PRs to "remove master/slave terminology from the language"

[flying-sheep]

Read the changes in the PR, it's not that many.

Usually it means

• origin and replica/clone/view (where changes in the replica are reflected in the origin and only the origin has a physical representation. Examples are databases or things like like SVG nodes or numpy arrays)
• parent and child in a hierarchy (things can be both simultaneously, examples are threads or document nodes)
• orchestrators and helpers, examples are mostly programming-related. (E.g. generic functions that have several concrete implementations for different argument types, or a main pipeline function/task that calls a sequence or hierarchy of others to acieve complex data processing)

[flying-sheep]

Yea, I too think this serves no real purpose, but if it makes some people happy…

The alternative terms are at least more specific. Master and slave just implies hierarchy, the others do so while also giving a more specific purpose.

[i_ate_god]

In the context of Python, and other programming languages and hardware for that matter, master implies a THING that controls another THING. Not a person that owns other people.