-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
BUG: df.plot.barh() broken from 1.1.5 to 1.2 under specific circumstances #39126
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
Hi, thanks for your report. This is a duplicate of #38947 |
The commit that caused the regression has been reverted. needs tests to prevent regressions |
@simonjayhawkins can I add test cases for this? |
Can someone please assign this issue to me? |
@thaisbendixen: You can assign this issue to yourself. Here are the instructions to do so (fourth paragraph): https://pandas.pydata.org/docs/development/contributing.html#where-to-start |
Hi, I want to pick this up, but just wanted to make sure it was still relevant and that I understand the requirements. We just want to have a test to help avoid this issue going forward? It seems like #46451 addressed the test issue. It uses So, are there additional test we want or is this good to close? |
#47306) * TST: barh plot with string and integer at the same column (#39126) * Update pandas/tests/plotting/test_misc.py Co-authored-by: Matthew Roeschke <[email protected]>
pandas-dev#47306) * TST: barh plot with string and integer at the same column (pandas-dev#39126) * Update pandas/tests/plotting/test_misc.py Co-authored-by: Matthew Roeschke <[email protected]>
I have checked that this issue has not already been reported.
I have confirmed this bug exists on the latest version of pandas.
(optional) I have confirmed this bug exists on the master branch of pandas.
Code Sample, a copy-pastable example
(executed as part of a notebook, but this should not matter)
Problem description
The code works in Pandas 1.1.5, but not in 1.2. I suppose that this is not intentional. Additionally, the bug seems to occur only when the first value is an integer and a following value cannot be parsed to an int. This probably goes rather deep into the library, so I cannot say whether barh is the actual problem or whether it lies somewhere else.
Stack trace
The text was updated successfully, but these errors were encountered: