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
At the moment, pynsee uses tqdm for progress bars.
It's a very solid library that does the job perfectly but it does not interact well with... basically anything.
So right now, any code or library using pynsee internally will have to accept having progress bars popping everywhere.
I think it would be nice to provide better options for handling them. I see to main options:
the simpler option is to provide one global parameter to hide progress (setting disable=True to the tqdm object)
switch to rich.progress, which, as far as I know, is the only library that supports nested progress bars; one would then have a global progress object that people could use to add other progress bars or simply disable them
The text was updated successfully, but these errors were encountered:
At the moment,
pynsee
usestqdm
for progress bars.It's a very solid library that does the job perfectly but it does not interact well with... basically anything.
So right now, any code or library using
pynsee
internally will have to accept having progress bars popping everywhere.I think it would be nice to provide better options for handling them. I see to main options:
disable=True
to the tqdm object)rich.progress
, which, as far as I know, is the only library that supports nested progress bars; one would then have a globalprogress
object that people could use to add other progress bars or simply disable themThe text was updated successfully, but these errors were encountered: