You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature related to a problem? Please describe it.
Summaries look great in Jupyter notebooks by default, but changing output options is clunky as it happens only in the to_string and to_html methods. For instance, there is no easy way to change the summary element to something other than "C" in a notebook because model.summary().to_html(element="N", names=True) will not render nicely by default.
Describe the solution you would like.
I would like the constructor to accept optional keyword arguments for those methods, enabling things like: model.summary(element="N", names=True).
Describe alternatives you considered
Wrapping everything in HTML(...) calls but this makes object inspection clunky.
Additional context
I'd be happy to provide a PR if other agree with this design.
The text was updated successfully, but these errors were encountered:
The original intent was that you can create different outputs from the same summary object. I would like to keep that behavior but the constructor arguments could certainly set the default if that's good enough for you?
Oh sorry. Never meant to remove them from the to_* methods. Just want them settable in the constructor as well. So they would set the default as you said.
Checklist
Is your feature related to a problem? Please describe it.
Summaries look great in Jupyter notebooks by default, but changing output options is clunky as it happens only in the
to_string
andto_html
methods. For instance, there is no easy way to change the summary element to something other than "C" in a notebook becausemodel.summary().to_html(element="N", names=True)
will not render nicely by default.Describe the solution you would like.
I would like the constructor to accept optional keyword arguments for those methods, enabling things like:
model.summary(element="N", names=True)
.Describe alternatives you considered
Wrapping everything in
HTML(...)
calls but this makes object inspection clunky.Additional context
I'd be happy to provide a PR if other agree with this design.
The text was updated successfully, but these errors were encountered: