8000 Avoid need to lock in dvi generation, to avoid deadlocks. by anntzer · Pull Request #17839 · matplotlib/matplotlib · GitHub
[go: up one dir, main page]
Skip to content

Avoid need to lock in dvi generation, to avoid deadlocks. #17839

New issue 8000

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Jul 5, 2020
Merged

Avoid need to lock in dvi generation, to avoid deadlocks. #17839

merged 1 commit into from
Jul 5, 2020

Conversation

anntzer
Copy link
Contributor
@anntzer anntzer commented Jul 5, 2020

Instead, generate the dvi in a temporary directory and move it to its
final path.

This should likely help with #7776 (comment) (although I don't have a repro for that issue).

PR Summary

PR Checklist

  • Has Pytest style unit tests
  • Code is Flake 8 compliant
  • New features are documented, with examples if plot related
  • Documentation is sphinx and numpydoc compliant
  • Added an entry to doc/users/next_whats_new/ if major new feature (follow instructions in README.rst there)
  • Documented in doc/api/next_api_changes/* if API changed in a backward-incompatible way

@anntzer
Avoid need to lock in dvi generation, to avoid deadlocks.
0efc44c 
Instead, generate the dvi in a temporary directory and move it to its
final path.
@anntzer anntzer added this to the v3.4.0 milestone Jul 5, 2020
@tacaswell tacaswell merged commit e2d0fa2 into matplotlib:master Jul 5, 2020
@anntzer anntzer deleted the unlock branch July 5, 2020 19:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@timhoffm timhoffm timhoffm approved these changes

Assignees
No one assigned
Labels
topic: text/usetex
Projects
None yet
Milestone
v3.4.0
Development

Successfully merging this pull request may close these issues.
3 participants
@anntzer @timhoffm @tacaswell
0