-
-
Notifications
You must be signed in to change notification settings - Fork 18.2k
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
Rework display logic again. #3663
Conversation
I did this in an xterm
worked but then
still displayed the full columns, should this have display the info display? as an aside, maybe I just don't understand but why do we have both is there a time when you would have them different? |
@y-p the deprecated message for |
@jreback , try now? max_info_columns is a limit for the summary view to prevent excessive Update: |
seemed to work, I had 2 feature requests:
|
re expand_frame_repr:
doesn't that match the description? re pd.set_option, option_context accepts option_context(pat,val,pat,val,...) we can add support for that, Would welcome your help on examples for the doc. |
@y-p sorry for slowness on my end, i'll take a look soon at this |
Verified that this fixed the "brokenness" I was experiencing in the IPython notebook (i.e. not being able to get the HTML view unless line_width was increased). Going to merge now and close the loop |
Thanks again, team, as always |
v0.11.0 introduced last-minute changes to the way the dataframe display logic works,
and they haven't proven themselves. The churn is unforunate, but if it's broken,
fix it.
height
is deprecated.max_rows solely determines the amount of rows displayed.
rebased on top of #3657.
Merging the previous PR and subsequent last minute fixes so close to the release
contributed to the problems only being discovered after the release.
So please test and report if this works for you, in terminal, qtconsole or notebook,
since the 0.11.1 release is so close.
cc @hayd , @lodagro ,@jreback