-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Backport PR #19108 on branch v3.3.x #19115
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
Backport PR #19108 on branch v3.3.x #19115
Conversation
Are you sure about that? The test is still failing. |
- HTMLWriter inherits from FileMovieWriter. - FileMovieWriter create a non-context manager TemporayDirectory on init. - The TemporayDirectory is cleaned up in the cleaup method of FileMovieWriter. - However this method (and its call chain through finish) try to either call a subprocess to merge a bunch of single-frame files into a movie (not relevant) or to clean up such a process (not relevant). - The least disruptive fix is to duplicate the file clean up code.
@QuLogic and I talked through this today. The issue is:
This code probably should on the main branch, we will handle that with a careful merge up. |
#18679 doesn't appear to have been backported, and I guess it basically fixed the bug that is now getting exposed by pytest? |
Further simplify pgf tmpdir cleanup. Backports matplotlib#18679 but drops the deprecation steps.
I tried to backport the non-deprecation related changes. I think I missed these failures locally because I have other pgf failures due to latex changing under us (I see this on Arch, assume we will see it in test containers eventually, but that is a problem for the future). |
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.
I have commits in here so leave it to the judgement of further reviewers if they they feel comfortable merging or wait for additional review.
Ah, sorry, I was looking at |
Backport PR #19108 on branch v3.3.x
In contrast to the original PR, no changes in tests are needed because we did not have tests that would trigger the warning back in 3.3.x.