You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The fact that it took so long for anyone to realise the behaviour had changed just goes to show that it is a very minor problem. I was pretty sure it used to work at one point so I chased it down. I'd say it is quite useful from time to time when you are working interactively and feeling lazy at the same time.
In case the behaviour change was not intentional I'd be willing to look into it but some pointers would be appreciated to get started.
The bugs I fixed had to do with using the color keyword. @lesteve the bug is a result of the fact that LinePlot always ends up assigning a color from a default or custom color cycle so when you plot consecutive Series it always uses the same color. The right thing to do is just to have it omit the color specification if unspecified and matplotlib will automatically choose a different color. Look forward to a PR!
With the 0.11 release scheduled in 4 days, I was wondering whether @wesm or @changhiskhan could have a quick look at the associated pull request. I completely understand this is a very minor bug which has easy work-arounds but still it would be nice if a fix could make it to the next release.
The fact that it took so long for anyone to realise the behaviour had changed just goes to show that it is a very minor problem. I was pretty sure it used to work at one point so I chased it down. I'd say it is quite useful from time to time when you are working interactively and feeling lazy at the same time.
In case the behaviour change was not intentional I'd be willing to look into it but some pointers would be appreciated to get started.
Here is a snippet:
Here is the output with pandas 0.8.0:
Here is the one with pandas 0.8.1:
The text was updated successfully, but these errors were encountered: