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.
PLT: plot('line') or plot('area') produces wrong xlim in xaxis in 0.25.0 #27993
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
PLT: plot('line') or plot('area') produces wrong xlim in xaxis in 0.25.0 #27993
Changes from 15 commits
7e461a1
1314059
8bcb313
df7011a
4df4905
ecd8c20
ace4003
f861067
f081d2b
f35653b
e807f3f
1627755
fd1d571
bb12de7
6a64b7f
67056f0
d4d6f2d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Can you expand on this? Perhaps open a new issue with the description of the bug, and reference it.
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.
Can you post images of the output for one of the failing tests, before and after your changes?
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.
@TomAugspurger yes, i feel the best way is to
xfail
the tests here and open up a new issue and do a follow-up PR to fix the tests, Because the main purpose is to test if thefinder
is being correctly used or not. And I honestly do not understand especially the second one in which there is avmin + 0.9
, I assume that's because of this wrong xaxis output, so has to manually add a constant to match the behavior.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.
After my change: (this is also aligned with the behaviour on matplotlib)
Before my change:(i feel this is a bit wrong, because plot should start from 1987Q2, while due to this error, it starts from Q3 IIUC)
@TomAugspurger
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.
Thanks... I think I agree with your assessment.
Can you open a new issue to discuss removing / updating those tests? And reference that in the skip / xfails?
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.
sure, i was thinking of doing it, but then i thought this PR would become a blocker for the issue if it is not merged because the test has to use the output of this PR. Probably I just overthink it ^^ thanks, will open and reference it. @TomAugspurger