Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork7.9k
fix FuncAnimation class#29967
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
fix FuncAnimation class#29967
Uh oh!
There was an error while loading.Please reload this page.
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.
Thank you for opening your first PR into Matplotlib!
If you have not heard from us in a week or so, please leave a new comment below and that should bring it to our attention. Most of our reviewers are volunteers and sometimes things fall through the cracks.
You can also join uson gitter for real-time discussion.
For details on testing, writing docs, and our review process, please seethe developer guide
We strive to be a welcoming and open project. Please follow ourCode of Conduct.
PR summary
Why is this change necessary?
To ensure the update function passed to FuncAnimation matches expected signatures and avoids runtime errors.
What problem does it solve?
It prevents type errors and ensures the animation updates frames correctly without freezing or crashing.
What is the reasoning for this implementation?
FuncAnimation requires different update function return types depending on blit, typing must reflect this to satisfy static checkers and runtime behavior.
Closes#29960
PR checklist