How to forward e.g. progress bars sent to stdout of the process to sys.stdout?

[sla-te]

sh.scp(
    "-i",
    "my_key",
    "a_file.tar.gz",
    "[email protected]:/target/folder",
    _out=sys.stdout, _err=sys.stderr,
)

This will block until the file transfer is complete and not print anything.

In case I add the special kwargs _unify_ttys=True, _tty_out=True, _tty_in=True the progress bar is printed once at 100% after the transfer is complete.

If I try to get hacky and try to adapt to https://sh.readthedocs.io/en/latest/tutorials/interacting_with_processes.html#tutorial2 like this:

aggregated = ""
aggregated_stdout = ""
def print_stdout(char, stdin):
    global aggregated_stdout
    aggregated_stdout += char

    if char == "\n" or "/s" in aggregated_stdout:
        print(aggregated_stdout, end="")
        aggregated_stdout = ""

aggregated_stderr = ""
def print_stderr(char, stdin):
    global aggregated_stderr
    aggregated_stderr += char
    print(char, end="", file=sys.stderr)

sh.scp(
    "-i",
    "my_key",
    "a_file.tar.gz",
    "[email protected]:/target/folder",
    _unify_ttys=True, _out=print_stdout, _err=print_stderr,
    _out_bufsize=0, _tty_in=True,, _tty_out=True, _tee=("out", "err")
)

Then I am pretty much getting what I want to see (the progress bar updating) but isnt there handling for such a scenario in sh?

[amoffat]

If you don't care about capturing the output, just use _fg=True and let the process write whatever it wants to the terminal. Otherwise, depending on how fancy the progress bar is, you'll need to process any special ascii characters yourself to render progress correctly. Programs that do progress bars typically write all kinds of invisible characters to jump around and re-render a progress bar.

[sla-te]

I think you are exaggerating massively, to my understanding and with regards to my other discussions I am rather heavily contributing to making the library more accessible for other users and am providing very helpful examples and questions, that will assist others and it should be more than obvious, that I have tried before and am not throwing empty tasks into discussions.

Anyway you are probably not the right person to speak as you are not the maintainer, so no hard feelings.

[ecederstrand]

I am in fact co-maintainer together with @amoffat. I'm happy for your contributions. I just don't have time to play around with ssh, scp and progress bars myself right now.

[sla-te]

Its perfectly fine if you don't have time to do it, hell it would even be ok if you said you don't care or don't want to. Conveying, that I am dropping of work for you to do for me gets me salty though, because I always try to open discussions or tickets in a way, that they will be useful for everyone, not only myself.

Look, I am not asking you to do anything, its an open source library - either you are interested in having more people using it and enriching it by helpful snippets others can use to start of or not. There are explanations for most commands in the docs but there are no examples for any actual use case whatsoever, which makes the approach very time consuming (and I believe I have already digged quite deep).

My approach was to post actual questions with actual approaches and snippets, instead of opening a discussion with the title "add more examples". If that's not sufficient, then I don't know.

[amoffat]

either you are interested in having more people using it ... or not.

@sla-te This is the second time you've expressed that us convincing you to use sh by helping you with your non-sh problems is actually aligned with our interests. It's not, and frankly we couldn't care less if you decided to use sh.

Unfortunately you have used up the remaining good will to help with whatever you are building. If you'd like to earn some of that good will back, you can make a PR with documentation improvements for the things that you figure out and would like to share with others. A good starting place might be a tutorial in the Tutorials Section

In the mean time, please don't make any more discussions.