-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
secondary_y plot shows in separate figure #9779
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
Hmm, it works if I do However, there are two bugs now:
|
Erm, executing the secondary_y line plot command first and the bar plot second solves issue 2. Now the plot has enough space for the bars. |
Another possibility is doing Providing the For the other questions, can you provide a small reproducible example? (some runnable code with some dummy data that shows the issue) |
Hmm, the two options you mention work indeed, though somehow I'm now missing the first plot's y axis ticks/labels and the second plot's legend altogether.. Here's the snippet with the shortened version (I was doing
On the other hand, using the following makes the second plot's legend overlap:
|
PS. This issue has now gone almost completely off-topic.. but still some issues I think :) |
@arski should be fixed now if you're comfortable running off master. Thanks for the report. |
Cool, thanks! What about the cut off first/last bars? |
Maybe make a separate issue for that bug, if we don't have one already. You can work around it with the ax.get_xlim() methos. |
@arski Because
|
ah, fair enough I guess, if only the legend order could be adjusted ;) |
Hi, don't know if this is my Python/some module version.. but when I try to do the following, I end up with two figures popping up, instead of the expected one:
The data in both plots looks right, the left/right y axes are correct etc.. but they're not on the same figure :(
Also if this is of any help, if I do
fig = plt.figure()
before running the commands above, I end up with another completely empty figure shown to me first..Sorry if this is something stupid and/or not caused by pandas..
The text was updated successfully, but these errors were encountered: