Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork7.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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
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 moveself.stale = True
into thepchanged
definition? It seems like every call topchanged
is followed byself.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
to76fcf6e
CompareHmm, 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. |
oscargus commentedJul 19, 2023 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
I moved all files other than artist.py to#26334. |
Uh oh!
There was an error while loading.Please reload this page.
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