From: Stefano Sabatini <stefasab@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] tools/zmqshell: port to python3
Date: Sun, 2 Apr 2023 17:14:06 +0200
Message-ID: <20230402151406.GF3542@mariano> (raw)
In-Reply-To: <20230401232112.GA10373@mariano>
On date Sunday 2023-04-02 01:21:12 +0200, Stefano Sabatini wrote:
> On date Wednesday 2023-03-29 00:06:40 -0400, Leo Izen wrote:
> > On 3/26/23 17:34, Stefano Sabatini wrote:
> > > Also extend docs, use argparse and logging.
> > > ---
> > > tools/zmqshell.py | 63 ++++++++++++++++++++++++++++++++++++++---------
> > > 1 file changed, 52 insertions(+), 11 deletions(-)
> [...]
> > > +def main():
> > > + parser = argparse.ArgumentParser(description=HELP, formatter_class=Formatter)
> > > + parser.add_argument('--bind-address', '-b', default='tcp://localhost:5555', help='specify bind address used to communicate with ZMQ')
> > > +
>
> > This changes the interface to use `--bind-address` instead of just passing
> > the address directly as argv[1]. Does this have the potential to break
> > anything downstream? Or do we make no promises about this interface?
>
> This is mostly meant for interactive use, so I'd rather keep things
> simple and drop the old syntax.
Pushed.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
prev parent reply other threads:[~2023-04-02 15:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-26 21:34 Stefano Sabatini
2023-03-28 22:08 ` Stefano Sabatini
2023-03-29 4:06 ` Leo Izen
2023-04-01 23:21 ` Stefano Sabatini
2023-04-02 15:14 ` Stefano Sabatini [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230402151406.GF3542@mariano \
--to=stefasab@gmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git