I've fixed this and released a 0.10.0 [1]. I'll work through updating global-requirements now. I would encourage moving away from both this extension and WSME in general as both have very little activity on them and I don't imagine that will change going forward. Chris Dent (CC'd) _might_ have some thoughts on how to approach this, but that's just a guess. Stephen [1] https://pypi.org/project/sphinxcontrib-pecanwsme/0.10.0/ On Tue, 2019-04-02 at 14:09 +0700, Renat Akhmerov wrote:
Ok, thanks. Good to know :)
Renat On 2 Apr 2019, 14:00 +0700, Eric Fried <openstack@fried.cc>, wrote:
Stephen has been going around fixing these. See for example https://review.openstack.org/#/c/648670/
I'm not sure about the maintainers/releases issue though.
efried
On Apr 2, 2019, at 01:13, Renat Akhmerov <renat.akhmerov@gmail.com> wrote:
Hi,
We have a problem with "openstack-tox-docs” CI job, see [1]. It seems like the new version of Sphinx (2.0.0) is not compatible with sphinxcontrib-pecanwsme 0.9.0.
Does anyone know how to better address this? I guess there needs to be a new version of sphinxcontrib-pecanwsme that fixes this bug but I’m not even sure that this project is maintained.
[1] http://logs.openstack.org/16/648316/6/check/openstack-tox-docs/3a2d588/job-o...
Thanks
Renat Akhmerov @Nokia