mirror of
https://github.com/theupdateframework/python-tuf
synced 2026-05-24 10:08:28 +00:00
0f59f4b749
Python version 3.6 was supported until December 23-rd 2021 meaning its end of life has expired before more than 20 days. Dropping support for python version 3.6 will allow us to remove OrderedDicts. After a quick check I saw that Warehouse target python version 3.8.2: - their docker file: https://github.com/pypa/warehouse/blob/main/Dockerfile#L47 - https://github.com/pypa/warehouse/blob/main/.python-version - last pr updating pr version: https://github.com/pypa/warehouse/pull/7828 Pip supports python version 3.7+ as well. They dropped python 3.6 a couple of months ago: https://github.com/pypa/pip/pull/10641 This means it shouldn't cause headache to our users if we drop python version 3.6 too. Signed-off-by: Martin Vrachev <mvrachev@vmware.com>
45 lines
1.7 KiB
Text
45 lines
1.7 KiB
Text
# TUF runtime requirements plus securesystemslib with extra dependencies
|
|
#
|
|
# This file together with 'pip-compile' is used to generate a pinned
|
|
# requirements file with all immediate and transitive dependencies.
|
|
#
|
|
# 'requirements-pinned.txt' is updated on GitHub with Dependabot, which
|
|
# triggers CI/CD builds to automatically test against updated dependencies.
|
|
#
|
|
#
|
|
# NOTE: 'pip-compile' only adds dependencies relevant for the Python version,
|
|
# in which it is executed. Moreover, it does not add environment markers of
|
|
# transitive dependencies.
|
|
# The official recommendation for cross-environment usage of pip-compile tends
|
|
# towards separate requirements files for each environment (see
|
|
# jazzband/pip-tools#651), this seem like an overkill for tuf, where we only
|
|
# have a few conditional dependencies, i.e. dependencies that are required on
|
|
# Python < 3 only.
|
|
#
|
|
#
|
|
# Below instructions can be used to re-generate 'requirements-pinned.txt', e.g.
|
|
# if:
|
|
# - requirements are added or removed from this file
|
|
# - Python version support is changed
|
|
# - CI/CD build breaks due to updates (e.g. transitive dependency conflicts)
|
|
#
|
|
# 1. Use this script to create a pinned requirements file for each Python
|
|
# version
|
|
# ```
|
|
# for v in 3.7 3.8 3.9; do
|
|
# mkvirtualenv tuf-env-${v} -p python${v};
|
|
# python3 -m pip install pip-tools;
|
|
# pip-compile --no-header -o requirements-${v}.txt requirements.txt;
|
|
# deactivate;
|
|
# rmvirtualenv tuf-env-${v};
|
|
# done;
|
|
#
|
|
# ```
|
|
# 2. Use this command to merge per-version files
|
|
# `sort -o requirements-pinned.txt -u requirements-?.?.txt`
|
|
# 2. Manually add environment markers to requirements-pinned.txt
|
|
# 3. Use this command to remove per-version files
|
|
# `rm requirements-?.?.txt`
|
|
#
|
|
securesystemslib[crypto, pynacl]
|
|
requests
|