Assign a default value for display max_seq_items

[ghost]

Perhaps I've opened a dupe issue in the past, can't find it.
pd.options.display.max_seq_items should not be None by default.
It's easy to hang the terminal by repr()ing with some mal-chosen data.
#3426

[cpcloud]

I set mine to 10 by default but that may be too small.

[ghost]

@jreback , @cpcloud , 0.12?

[jreback]

up2u

[cpcloud]

i could take care of this in the pr i have for repring large sequences but i don't think i'm going to be able to finish it by 0.12...

[ghost]

please do. if it doesn't make it, no problem.

[jreback]

@cpcloud 0.13 or push?

[cpcloud]

0.13

[jtratner]

I kinda wish we could add defaults to config options (i.e., if I'm not defined, use this other config option instead), then we could have this default to max_rows. Does add some complexit.

[jreback]

is this the same as max_rows? (or is this applicable for something else?)

[cpcloud]

no this is different

this for repring large sequences (in general, MultiIjndex, Index, lists, dicts, etc)

max rows is for a frame summary

[jreback]

what's the problem with None? then its computed right?

[cpcloud]

no ... it's unlimited if it's None, so a huge index will take forever to repr

[jreback]

ahh...I see...why don't we just put a sensible value as th edefault, maybe 100?

[jreback]

I don't have this set as a matter of fact...and the unlimited is annoying

[cpcloud]

yep that's what i've done (pr is up , but i haven't touched it in a while)... there's a tiny issue with using this with max_edge_items .. i'll get it ready for 0.13

[jreback]

gr8

[jreback]

@cpcloud this and max_edge_items?

[jreback]

@cpcloud push?

[jreback]

@cpcloud ?