[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230321105203.0dfc7a00@kernel.org>
Date: Tue, 21 Mar 2023 10:52:03 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: "Michalik, Michal" <michal.michalik@...el.com>
Cc: Edward Cree <ecree.xilinx@...il.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"davem@...emloft.net" <davem@...emloft.net>,
"pabeni@...hat.com" <pabeni@...hat.com>,
"edumazet@...gle.com" <edumazet@...gle.com>,
"Kubalewski, Arkadiusz" <arkadiusz.kubalewski@...el.com>
Subject: Re: [PATCH net] tools: ynl: add the Python requirements.txt file
On Tue, 21 Mar 2023 12:34:50 +0000 Michalik, Michal wrote:
> > Assuming the libraries are following best practice for their version
> > numbering (e.g. semver), you should be able to use ~= ('compatible
> > version' [1]).
> > For example, `jsonschema ~= 4.0` will allow any 4.x.y release, but
> > not 5.0.0 since that could have breaking API changes.
> > I would recommend against pinning to a specific version of a
> > dependency; this is a development tree, not a deployment script.
>
> This is actually a good idea. Let's wait for Jakub to confirm if he feels
> the Python requirements file is a good idea in this case. If he confirms,
> I would update the libraries according to your suggestion. Thanks.
Given the "system script" nature of the project (vs "full application")
I don't find the requirements to be necessary right now. But I don't
know much about Python, so maybe Ed can make a call? :D
Powered by blists - more mailing lists