A new release of dnspython has been release, which is breaking the docs
tests. See [1]
dnspython is fixed to <2.3.0 in upper-constraints, so we should rely on
requirements.txt from mistral to trigger the correct build.
[1] https://github.com/eventlet/eventlet/issues/781
Signed-off-by: Arnaud Morin <arnaud.morin@ovhcloud.com>
Change-Id: I5f86f8264792c8e651c0bb2d2f63151657fea1be
Switch to openstackdocstheme 2.2.1 and reno 3.1.0 versions. Using
these versions will allow especially:
* Linking from HTML to PDF document
* Allow parallel building of documents
* Fix some rendering problems
Update Sphinx version as well.
Set openstackdocs_pdf_link to link to PDF file. Note that
the link to the published document only works on docs.openstack.org
where the PDF file is placed in the top-level html directory. The
site-preview places the PDF in a pdf directory.
Disable openstackdocs_auto_name to use 'project' variable as name.
Change pygments_style to 'native' since old theme version always used
'native' and the theme now respects the setting and using 'sphinx' can
lead to some strange rendering.
Remove docs requirements from lower-constraints, they are not needed
during install or test but only for docs building.
openstackdocstheme renames some variables, so follow the renames
before the next release removes them. A couple of variables are also
not needed anymore, remove them.
Remove python 3 versioning from lower-constraints and
requirements to pass requirements-check.
See also
http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014971.html
Change-Id: Id478711abb1783422ebb4ee9937d1b7202fdf2f3
* This patch also adds handling for iterators in the sanitizing
function for YAQL results. JSON serialization for iterators now
works correctly but the issue is that they can be used only once.
So, for example, if we got a result from YAQL and performed JSON
serialization for it, then the iterator is already empty and
the data structure is just corrupted. So we can't further pass
to executors and other subsystems. The solution is just to sanitize
iterators after they're just returned from YAQL.
* Added a test to make sure that action input reaches an executor
not corrupted, although it gets saved into DB and hence serialized
into JSON.
* Changed the Sphinx entry in requirements.txt so that the version
3.0.0 is now excluded (it breaks the build).
Closes-Bug: #1871567
Change-Id: I47abe0904b49d72e33eb10080c71fb81980d44da
Sphinx 1.8 introduced [1] the '--keep-going' argument which, as its name
suggests, keeps the build running when it encounters non-fatal errors.
This is exceptionally useful in avoiding a continuous edit-build loop
when undertaking large doc reworks where multiple errors may be
introduced.
[1] https://github.com/sphinx-doc/sphinx/commit/e3483e9b045
Change-Id: Ife98c47af59355540fa30d7ca762f857759c1274
Some minor updates including fixing issues with the HTML5 output
generated by Sphinx 2.0, inlining the OpenStack logo rather than
referencing it from elsewhere, and adding a new SOURCE_DATE_EPOCH option
for use in reproducible builds in new release openstackdocstheme 1.30.0.
...to pick up many improvements, including the return of table borders.
Change-Id: I22b652e1eb007616e697cb238fcd9e5f010cd693
NetworkX released 2.3, dropping support for Python 2.
https://github.com/networkx/networkx/blob/master/doc/news.rst
Also see I0a9700926c9a0db93e782c853c33f1aaee3d4876
fixed sphinx requirements also according to global requirements
jsonschema should be uncaped also according to global requirements
but there are conflicts with zakarclient designateclient and irconicclient
so for now I put it in remark
Change-Id: Iea3dbcfa1f6ddf2c413ede5e73fa076c6edccfdf
Arnaud Morin