930dd24dd2
Sphinx was pinned to >1.5.0 <=1.7.0 4 years ago. It is now on v4.4.0,
and we're seeing an incompatibility with the latest version of jinja2.
Along with updating the Sphinx version, this also includes fixes for
several warnings generated in the latest version:
* Outdated docs due to the removal of the "parser" param from
Base.get_xml
* Class lookup issues
* External links for which we have extlinks defined
* Deprated PyModulelevel is replaced by PyFunction
* sphinx.ext.autodoc.Documenter.get_doc signature changed
Signed-off-by: Eric Ball <eball@linuxfoundation.org>
Change-Id: Iba65fb724f098f3e4a0b20f2a183cb2ea3c450ea
16 lines
564 B
Plaintext
16 lines
564 B
Plaintext
# 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.
|
|
|
|
coverage>=4.0 # Apache-2.0
|
|
fixtures>=3.0.0 # Apache-2.0/BSD
|
|
python-subunit>=0.0.18 # Apache-2.0/BSD
|
|
sphinx>=4.4.0
|
|
testscenarios>=0.4 # Apache-2.0/BSD
|
|
testtools>=1.4.0 # MIT
|
|
stestr>=2.0.0,!=3.0.0 # Apache-2.0/BSD
|
|
tox>=2.9.1 # MIT
|
|
mock>=2.0; python_version < '3.0' # BSD
|
|
sphinxcontrib-programoutput
|
|
pluggy<1.0.0 # the last version that supports Python 2
|