diff options
author | Michal Michalik <michal.michalik@intel.com> | 2023-03-23 20:08:02 +0100 |
---|---|---|
committer | Jakub Kicinski <kuba@kernel.org> | 2023-03-24 19:11:02 -0700 |
commit | bc77f7318da8812244cd2329d0bfc1312e75cfd9 (patch) | |
tree | a24cb7e92e03e00ae5a2a552e4b965405f552da3 /samples | |
parent | 2d08f3e128b1b380b0992ab40d60e0843db3c6b2 (diff) | |
download | linux-stable-bc77f7318da8812244cd2329d0bfc1312e75cfd9.tar.gz linux-stable-bc77f7318da8812244cd2329d0bfc1312e75cfd9.tar.bz2 linux-stable-bc77f7318da8812244cd2329d0bfc1312e75cfd9.zip |
tools: ynl: add the Python requirements.txt file
It is a good practice to state explicitly which are the required Python
packages needed in a particular project to run it. The most commonly
used way is to store them in the `requirements.txt` file*.
*URL: https://pip.pypa.io/en/stable/reference/requirements-file-format/
Currently user needs to figure out himself that Python needs `PyYAML`
and `jsonschema` (and theirs requirements) packages to use the tool.
Add the `requirements.txt` for user convenience.
How to use it:
1) (optional) Create and activate empty virtual environment:
python3.X -m venv venv3X
source ./venv3X/bin/activate
2) Install all the required packages:
pip install -r requirements.txt
or
python -m pip install -r requirements.txt
3) Run the script!
The `requirements.txt` file was tested for:
* Python 3.6
* Python 3.8
* Python 3.10
Signed-off-by: Michal Michalik <michal.michalik@intel.com>
Link: https://lore.kernel.org/r/20230323190802.32206-1-michal.michalik@intel.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'samples')
0 files changed, 0 insertions, 0 deletions