-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
plot forces ordering on Datetimeindex #3642
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
Comments
@y-p whats the deal on this? |
huh? |
just wanted to see if should bump to 0.12 |
why don't we just add a keyword, maybe |
I don't have an easy way of testing these kind of things (and that is why I don't really get involved in plotting)....I am just a user here :) for some reason I can't import the dev version (the one I am working on) into my ipython notebook.....how do you do it? |
I think you want |
yep...thankks |
Shelving for the release candidate, maybe push to 0.12. |
This is about a change introduced for 0.11.1, so moving back the decision Seems it's either:
I seem to be in the minority in thinking this was the wrong solution, so 2 is fine by me. |
@dieterv77, I'd like to revert #3619 and convert into a new issue to make this Does that sound reasonable? |
are there cases where the old behavior is what you want? |
not really. I can imagine that in some RTL locales, ascending vs descending order of sorting enough. I'm not championing this anymore. |
introduced by #3619, opening this to track the issue for 0.11.1.
While the user should be able to get sorted ticks when plotting, it should not
be forced on him. so either opt-in or opt-out but not "one size fits all".
The text was updated successfully, but these errors were encountered: