kernelci.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: Tim Bird <tim.bird@sony.com>
Cc: "guillaume.tucker@collabora.com" <guillaume.tucker@collabora.com>,
	"kernelci@lists.linux.dev" <kernelci@lists.linux.dev>,
	"automated-testing@lists.yoctoproject.org"
	<automated-testing@lists.yoctoproject.org>
Subject: Re: [Automated-testing] kci command line poll: Click or Typer?
Date: Fri, 22 Sep 2023 09:59:03 +0200	[thread overview]
Message-ID: <ZQ1JRywfnmUB0tdb@yuki> (raw)
In-Reply-To: <BYAPR13MB2503E4A7D66BEFE5B8E95B30FDF8A@BYAPR13MB2503.namprd13.prod.outlook.com>

Hi!
> I see exactly 0% of the people saying to stay with argparse, but that would be my recommendation.
> The rationale for this is that argparse is old and unlikely to be changed in an incompatible way in
> some future version of Python. 

+1

We recently started to work on new tooling for running LTP tests written
in python and after a few up and downs we ended up with using the bare
minimum of modules we can get away with. Less is clearly more in this
context.

-- 
Cyril Hrubis
chrubis@suse.cz

  parent reply	other threads:[~2023-09-22  7:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-21  8:59 kci command line poll: Click or Typer? Guillaume Tucker
2023-09-21 19:41 ` [Automated-testing] " Bird, Tim
2023-09-21 20:17   ` Richard Purdie
2023-09-21 20:48     ` Mark Brown
2023-09-21 21:46       ` Bird, Tim
2023-09-22  7:24         ` Robert Schwebel
2023-09-22  7:59   ` Cyril Hrubis [this message]
2023-09-25  7:23     ` Guillaume Tucker
2023-09-25  7:12   ` Guillaume Tucker
2023-10-03  8:17 ` Guillaume Tucker

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=ZQ1JRywfnmUB0tdb@yuki \
    --to=chrubis@suse.cz \
    --cc=automated-testing@lists.yoctoproject.org \
    --cc=guillaume.tucker@collabora.com \
    --cc=kernelci@lists.linux.dev \
    --cc=tim.bird@sony.com \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).