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
ERR: DataFrame can get into unprintable state #16098
Comments
Same problem (the stack traces match) good_df = pd.DataFrame({'three': [3]})
bad_df = pd.DataFrame({'three': [3, 3]})
df1 = pd.DataFrame({
'x': [1, 2, 3],
'y': [1, '2', [good_df]]
})
df2 = pd.DataFrame({
'x': [1, 2, 3],
'y': [1, '2', [bad_df]]
})
# df1 can be printed
# df2 raises a StopIteration exception when printed |
I have the same error |
I also have this problem. Basically, it means that Series or DataFrames with embedded dict-of-DataFrames cannot be printed — they are either printed with wrong value (case 1 below) or raises an error (case 2 below). I think priority should be raised. My reproducer:
|
Note: list-of-DataFrames have the same problem as dict-of-DataFrames, which links this to the original report.
|
And finally (sorry for the noise) — I see that the prio-low label was already removed. So that's already good :) |
anyone one in the community can submit a PR - this is how issues are solved there is no priority was there are no resources to allocate - pandas is all volunteer |
I understand that @jreback, it was just that I (mistakenly) thought it was tagged as "Prio-low" which felt wrong. edit: to clarify, felt wrong because it would discourage volunteers from working on it, not wrong because someone should be forced to prioritize it. |
I know my replication case looks very strange, I had a typo assigning the wrong thing to
index=
, but the way the error is reported out of this made it very confusing to debug, possibly can do something better:Code Sample, a copy-pastable example if possible
pandas
0.19.1
The text was updated successfully, but these errors were encountered: