-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Only do pchanged and set stale when value changes + doc consistency #26326
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
Conversation
self.pchanged() | ||
self.stale = True |
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.
For a follow-up PR I wonder if we should move self.stale = True
into the pchanged
definition? It seems like every call to pchanged
is followed by self.stale = True
...
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.
That can for sure be a good idea.
87098e3
to
76fcf6e
Compare
Hmm, most of this seems like it should be in #26334? |
Sort of. I stopped adding those here and started a new PR. I can possibly move individual files to that PR instead. |
76fcf6e
to
59dbd1e
Compare
I moved all files other than artist.py to #26334. |
59dbd1e
to
fdcaafc
Compare
fdcaafc
to
439cf08
Compare
anyone can merge what green |
PR summary
Original purpose was to not call pchanged or set stale to True if the value did not change (some set-methods already do this).
However, I found some doc inconsistencies so did a bit of search-and-replace as well...
PR checklist