feat: show progress messages on initialization, for reassurance #41
Conversation
|
I might be able to help with this, I recently was playing around with progress bars using the Perhaps an indexing progress bar would give the feedback you were looking for? If so, I will speak to @moleculekayak about any implementation details he might have in mind. |
| print(f"\rStarting up. Collecting infohashes...") | ||
| print(f"\rFound {len(files)} files to process...") |
There was a problem hiding this comment.
Just for my curiosity, what's the purpose of the carriage returns at the start of the lines? Since print includes a newline, shouldn't the carriage return be unneeded?
There was a problem hiding this comment.
You are right, the only \r that is truly needed is the one in print(f"\r({processed}/{len(files)})…
because it is trying to overwrite the current output line.
|
@zakkarry honestly, I'm okay with this approach. It's simple and doesn't include any addl. deps. Thoughts? |
If keeping the dep surface down is a desire, than I agree. I will say that my main reason for bringing it up is that I recently used them and not much more. The amount of effort in getting the callback and displaying of the bars consistent with something like rich or progress is pretty incongruent with the benefits it provides being brief, aesthetic, and not much more. Perhaps just a timer, though, to signify that it isn't frozen? Then when complete you can see how long the processing took at least and know that it did not freeze. |
3 participants
When starting up, thousands of files can take a long time to read, and there's no screen output.
Suggested: a welcome message and progress indicator, so user knows the program started successfully and not hung on start.