Use keyword arguments for setp() in examples #10155
Merged
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
QuLogic
approved these changes
Jan 4, 2018
Contributor
|
@meeseeksdev backport to v2.1.1-doc |
anntzer
added a commit
that referenced
this pull request
Jan 4, 2018
Backport PR #10155 on branch v2.1.1-doc
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Suggestio
2BF7
n cannot be applied right now. Please check back later.
PR Summary
Migrate
setp()usage in examples from MATLAB-like name-val positional arguments to keyword arguments.Motivation: Keyword arguments are clearer, safer and more pythonic. We want to encourage their use over the alternative MATLAB-like API of
setp(). All examples should thus use the keyword-API.