requirements.in

# One hash-pinned lockfile per supported Python LTS lives under
# `lockfiles/pyXX/requirements.txt` (`py39` ... `py314`). Pick the
# one that matches the local Python version when reproducing a CI run
# or vendoring downstream. Each subdirectory under `lockfiles/` is a
# separate Dependabot watchpoint, except `lockfiles/py39/` which is
# excluded from Dependabot (most upstream packages dropped Python
# 3.9 over 2025/2026; Dependabot does not honour `requires_python`
# when proposing bumps, so every PR against py39 would break RHEL 8
# / Debian 11). The py39 lockfile is regenerated manually as needed.
#
# To regenerate all of them:
#
#   for v in 3.9 3.10 3.11 3.12 3.13 3.14; do
#     python${v} -m venv .venv-py${v//.}
#     ./.venv-py${v//.}/bin/python -m pip install 'pip<25.1' pip-tools
#     mkdir -p lockfiles/py${v//.}
#     ./.venv-py${v//.}/bin/python -m piptools compile --generate-hashes \
#         --output-file=lockfiles/py${v//.}/requirements.txt requirements.in
#   done

beautifulsoup4
httpx[http2]
lxml --only-binary=lxml
netifaces
psutil
pymysql
pypsrp
PySmbClient
pywinrm
smbprotocol
xmltodict