Consistently name callback arguments event instead of evt #16099
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I found some more
Did you exclude these intentionally? |
The following occurrences are in technically public functions. If we go by the book, we would need a deprecation (even though I think hardly anybody will use these, and even less so with
|
6 tasks
|
ping @dopplershift I've addressed your concerns as far as possible. |
dopplershift
approved these changes
Feb 13, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Summary
Changes are only made to examples and internal methods, so no deprecation necessary.
This addresses:
eventas variable name (c.f. second code example at https://wxpython.org/Phoenix/docs/html/events_overview.html)