Gpiozero: Build docs warnings

Created on 10 Feb 2019  路  5Comments  路  Source: gpiozero/gpiozero

I just followed the instructions here on my Ubuntu 16.04 PC, and when I run make doc I get a whole load of scary-looking warnings displayed in my terminal (in red), along the lines of:

Running Sphinx v1.8.4
making output directory...
loading intersphinx inventory from https://docs.python.org/3.5/objects.inv...
loading intersphinx inventory from https://picamera.readthedocs.io/en/stable/objects.inv...
WARNING: failed to reach any of the inventories with the following issues:
WARNING: intersphinx inventory 'https://picamera.readthedocs.io/en/stable/objects.inv' not fetchable due to <class 'requests.exceptions.HTTPError'>: ('intersphinx inventory %r not fetchable due to %s: %s', 'https://picamera.readthedocs.io/en/stable/objects.inv', <class 'requests.exceptions.HTTPError'>, HTTPError(...))
loading intersphinx inventory from https://colorzero.readthedocs.io/en/stable/objects.inv...
WARNING: failed to reach any of the inventories with the following issues:
WARNING: intersphinx inventory 'https://colorzero.readthedocs.io/en/stable/objects.inv' not fetchable due to <class 'requests.exceptions.HTTPError'>: ('intersphinx inventory %r not fetchable due to %s: %s', 'https://colorzero.readthedocs.io/en/stable/objects.inv', <class 'requests.exceptions.HTTPError'>, HTTPError(...))

Am I missing some dependency, or are these harmless warnings that can be ignored?

question

Most helpful comment

It is harmless, but I fixed it anyway in a commit just before release (just added a placeholder file as git won't track empty dirs).

All 5 comments

@waveform80 has done considerable work in the docs-tidy-up branch recently. I think most/all such warnings will have gone away now.

Yup, switching to the docs-tidy-up branch gets rid of the intersphinx warnings :+1: Sorry I didn't try that earlier!
But there's now a red warning that copying static files... WARNING: html_static_path entry '/home/qpc/python-gpiozero/docs/_static' does not exist ?

Does this being closed imply that the warning is indeed harmless? :)

I believe so

It is harmless, but I fixed it anyway in a commit just before release (just added a placeholder file as git won't track empty dirs).

Was this page helpful?
0 / 5 - 0 ratings

Related issues

bootsmann picture bootsmann  路  8Comments

lurch picture lurch  路  12Comments

bsimmo picture bsimmo  路  6Comments

e28eta picture e28eta  路  4Comments

waveform80 picture waveform80  路  11Comments