Replies: 4 comments 6 replies
-
Hi Paul, Yeah, I think this is a good idea. |
Beta Was this translation helpful? Give feedback.
1 reply
-
After writing that post, I think I'll just do a PR that adds the classmethod. "..." as a parameter might be sexy, but it defies typing, so I take that as a sign. |
Beta Was this translation helpful? Give feedback.
4 replies
-
Hrmmmm, PR failed to build. "Works on my machine." |
Beta Was this translation helpful? Give feedback.
1 reply
-
PR merged - next release will have get_default_columns() classmethod on Progress. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
rich.progress.Progress uses these columns as default if no columns are specified:
If I just want to specify some extensions, I have to give the whole list of columns, including the defaults. For instance, to add a Spinner before and a TimeElapsed after, I have to do this:
Wouldn't it be a friendlier API to accept
...
as a value indicating "default columns here", so that this same code could be written as:Or as a more conventional option, define the default columns as a classmethod:
Just so I don't have to hard-code the default columns in my own code.
Beta Was this translation helpful? Give feedback.
All reactions