Revert #22360: Let TeX handle multiline strings itself#24047
Merged
timhoffm merged 4 commits intomatplotlib:mainfrom Oct 2, 2022
Merged
Revert #22360: Let TeX handle multiline strings itself#24047timhoffm merged 4 commits intomatplotlib:mainfrom
timhoffm merged 4 commits intomatplotlib:mainfrom
Conversation
502ce23 to
bcd8232
Compare
Member
Author
|
I added a simplified version of the code in the original report that worked in 3.5.3, failed on |
anntzer
approved these changes
Oct 1, 2022
timhoffm
approved these changes
Oct 2, 2022
meeseeksmachine
pushed a commit
to meeseeksmachine/matplotlib
that referenced
this pull request
Oct 2, 2022
… multiline strings itself
This was referenced Oct 6, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR Summary
As suggested by @anntzer in #23977, this revert #22360 and also reverts #22361. For #22360, I only reverted the first two commits. As far as I could tell, the third and fourth commits are just stylistic changes, and subsequent PRs made them conflict even more, so I did not want to try to disentangle them.
Not sure about the test, should I just use the code from #23977 in an image test?
PR Checklist
Tests and Styling
pytestpasses).flake8-docstringsand runflake8 --docstring-convention=all).Documentation
doc/users/next_whats_new/(follow instructions in README.rst there).doc/api/next_api_changes/(follow instructions in README.rst there).