[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46b182e9-bff5-2e5d-e3d6-27eb466657ef@gmail.com>
Date: Tue, 21 Mar 2023 18:52:24 +0000
From: Edward Cree <ecree.xilinx@...il.com>
To: Jakub Kicinski <kuba@...nel.org>,
"Michalik, Michal" <michal.michalik@...el.com>
Cc: "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 21/03/2023 17:52, Jakub Kicinski wrote:
> Given the "system script" nature of the project (vs "full application")
> I don't find the requirements to be necessary right now.
I'd say it's good to document the dependencies, because otherwise
getting it to run could be a PITA for the user; poking around I
don't see a convenient readme that could have a note added like
"This tool requires the PyYAML and jsonschema libraries".
And if you're going to add a document just for this then it *may
as well* be in the machine-readable format that pip install can
consume.
> But I don't know much about Python, so maybe Ed can make a call? :D
I'm not exactly an expert either :D
Powered by blists - more mailing lists