things I tried:
- changing the offending string, but even if i just used 'foobar', Sphinx emitted that warning. If I removed the entire LOG.warning line, it was fine.
- suppressing all known/documented sphinx warnings via 'suppress_warnings' in our conf.py file [1]. Sphinx still emitted the warning.
I don't want to look at the sphinx code, but it seems to me that 1.6.2 is the culprit. mjturek mentioned that yesterday when it was working, we were using sphinx 1.5.6 in gate...
things I tried:
- changing the offending string, but even if i just used 'foobar', Sphinx emitted that warning. If I removed the entire LOG.warning line, it was fine.
- suppressing all known/documented sphinx warnings via 'suppress_warnings' in our conf.py file [1]. Sphinx still emitted the warning.
I don't want to look at the sphinx code, but it seems to me that 1.6.2 is the culprit. mjturek mentioned that yesterday when it was working, we were using sphinx 1.5.6 in gate...
[1] http:// www.sphinx- doc.org/ en/stable/ config. html, see 'suppress_ warnings' .