-
-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reduce amount of usage of "dummy" in codebase to minimum #2547
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agreed with your intent after reading the linked documents to avoid the term 'dummy'.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# Conflicts: # src_c/_sprite.c # src_c/cython/pygame/_sprite.pyx
I was initially going to save these for another PR, but there were actually only a few (I realised once I deleted the generated documentation). So I've bundled them in as well. Now the only remaining instances of dummy are all related to the SDL video driver. I suspect SDL will be unable to simply rename this simply as it is a string used all over the place in other people's code. Other potential ideas:
|
partially fixes #1218 - may be about as good code-side as we can do code side due to relying on external libraries which will struggle to change over things due to public API.
Motivation
See: https://developers.google.com/style/inclusive-documentation for one example, but there are other similar inclusive language style guides.
This guide recommends 'placeholder variable' where we might currently use 'dummy variable'. Pandas had a long back and forth on the topic here. I'm aware not everyone will agree with this but it seems a fairly easy switch to reduce our exposure on this topic.