Html repr with JupyterLab TOC

[newville]

]

Description

This should replace #883, and follows from discussion #884

Type of Changes

• Bug fix
• New feature
• Refactoring / maintenance
• Documentation / examples

Tested on

Verification

Have you

• included docstrings that follow PEP 257?

• referenced existing Issue and/or provided relevant link to mailing list?

• verified that existing tests pass locally?

• verified that the documentation builds locally?

• squashed/minimized your commits and written descriptive commit messages?

• added or updated existing tests to cover the changes?
• updated the documentation and/or added an entry to the release notes (doc/whatsnew.rst)?
• added an example?

[codecov]

Codecov Report

Merging #902 (37e22ce) into master (4968ef2) will decrease coverage by 0.01%.
The diff coverage is 93.33%.

@@            Coverage Diff             @@
##           master     #902      +/-   ##
==========================================
- Coverage   93.23%   93.23%   -0.01%     
==========================================
  Files          10       10              
  Lines        3683     3693      +10     
==========================================
+ Hits         3434     3443       +9     
- Misses        249      250       +1     

Impacted Files	Coverage Δ
lmfit/minimizer.py	89.83% <0.00%> (-0.10%)	⬇️
lmfit/model.py	91.25% <100.00%> (ø)
lmfit/printfuncs.py	97.92% <100.00%> (+0.06%)	⬆️

[eendebakpt]

For reference: the old representation (in JupyterLab):

and the one with this PR:

[eendebakpt]

The PR addresses the issue from #883 (e.g. the lmfit output adding many sections to the table of contents). The formatting style is off course subjective, but it looks good to me.

The only thing that bothers me a bit is the final caption (for Correlations) that is split between two lines for no apparent reason.

[newville]

@eendebakpt I updated the HTML generation to have column headers for the correlation table, which should help, and to left-align most of the text.

If you find this acceptable, I'll merge this in.

[reneeotten]

@newville looks good to me! Can you please do a "squash-and-merge" and update the commit message so we're not left with all the mess (after all this should just be one commit anyway) 😉

[newville]

@reneeotten yep, I will squash and merge.