Files
019bade19cd20aaebb6dd1f423ab2dbb15cd12a1
swift /doc /requirements.txt

11 lines
464 B
Plaintext
Raw Normal View History

# The order of packages is significant, because pip processes them in the order
# of appearance. Changing the order has an impact on the overall integration
# process, which may cause wedges in the gate later.
# this is required for the docs build jobs
Remove <py3.5 dependencies from requirements.txt The requirements repo is support python 3.5 as oldest python version while swift still supports py27. thus, requirements-check will fail on a couple of lines in swift. The check is only run when these files are touched. The py2.7 packagers we know about aren't depending on upstream requirements.txt for correctness and aside from all the production deployments running on py2.7 we only realistically support >=py3.7 There's no good reason for our requirements.txt to be "unspported" by the openstack requirements check job. Since they only support >=py3.5 we can change our requirements.txt inline with that. This should be fine for everything we could hope to get out of both our requirements.txt and the check! Co-Authored-By: Clay Gerrard <clay.gerrard@gmail.com> Change-Id: Ibf8000498528c401707be8b0b91b8355cd993786
2020年06月02日 21:42:05 +02:00
sphinx>=1.6.2 # BSD
openstackdocstheme>=1.30.0 # Apache-2.0
reno>=1.8.0 # Apache-2.0
os-api-ref>=1.0.0 # Apache-2.0
python-keystoneclient!=2.1.0,>=2.0.0 # Apache-2.0
sphinxcontrib-svg2pdfconverter>=0.1.0 # BSD