Add requirements.txt file

[Mab879]

Description:

Add a requirements.txt file with the Python packages that are not in the Fedora repos.

Rationale:

Make it easier to install the python dependacies.

[github-actions]

Start a new ephemeral environment with changes proposed in this pull request:

Fedora Environment

Oracle Linux 8 Environment

[codeclimate]

Code Climate has analyzed commit a55b7eb and detected 0 issues on this pull request.

The test coverage on the diff in this pull request is 100.0% (50% is the threshold).

This pull request will bring the total coverage in the repository to 52.4% (0.0% change).

View more on Code Climate.

[rhmdnd]

Thanks for proposing this, Matt.

[rhmdnd]

Looks like we'll need:

• PyYAML
• jinja2
• pandas (although this is from the tool I'm writing, so I can add it there if this lands first)
• tables
• openpyxl
• pygments

[Mab879]

Looks like all of those packages are in the Fedora repos (and most are in RHEL). The current scope of this PR is only for packages not in Fedora. These would be good add to your PR in #10474.

PyYAML -> python3-pyyaml
jinja2 - > python3-jinja2
pandas -> python3-pandas
tables -> python3-tables That's not currently in our docs, can you cite which script needs this?
openpyxl -> python3-openpyxl
pygments -> python3-pygments, also not in our docs

[rhmdnd]

Ok - good deal. Thanks.

[matejak]

Don't be shy and add them as well - if you use pip install on a system where part of the requirements are already satisfied, they are simply skipped.

[Mab879]

Helps address #7988

[rhmdnd]

I have a patch for introducing a test-requirements.txt file, too #10487

Another approach we could take to help keep dependencies orthogonal would be to group scripts in directories. For example, we could have utils/build/ and utils/development/. The scripts dedicated to build pipelines or function would live in build/ and everything else necessary for helping contributors write and maintain content could live in development/.

From there, it would be relatively easy for contributors to have virtualenvs for dev and build separately (e.g., utils/development/requirements.txt). That may or may not be useful.

A side effect is that it would be nice to group like tools together, which may lead to efforts to consolidate functionality or consider moving to a unified, intuitive tool set for development.

[Mab879]

Succeed by #10487