cubicweb #17260732 is documentation built broken? [in-progress]

Hello,

As decribe in this email https://lists.cubicweb.org/pipermail/cubicweb-devel/2019-December/110884.html it really looks like the documentation built is broken.

Email:

--

Hello,

I've tried building the documentation using python3 out of cursiosity and ended up with those encoding errors:

mkdir -p js_api
tools/pyjsrest.py -p ../cubicweb/web/data -o js_api
tools/pyjsrest.py:118: DeprecationWarning: 'U' mode is deprecated
  filecontent = open(js_filepath, 'U').read()
Traceback (most recent call last):
  File "tools/pyjsrest.py", line 159, in <module>
    parse_js_files()
  File "tools/pyjsrest.py", line 92, in parse_js_files
    f_rst.write(rst_content)
TypeError: a bytes-like object is required, not 'str'
make: *** [Makefile:50: js] Error 1

And (after fixing the previous one):

mkdir -p js_api
tools/pyjsrest.py -p ../cubicweb/web/data -o js_api
tools/pyjsrest.py:118: DeprecationWarning: 'U' mode is deprecated
  filecontent = open(js_filepath, 'U').read()
Traceback (most recent call last):
  File "tools/pyjsrest.py", line 159, in <module>
    parse_js_files()
  File "tools/pyjsrest.py", line 86, in parse_js_files
    rst_content =  extract_rest(js_path, js_file)
  File "tools/pyjsrest.py", line 118, in extract_rest
    filecontent = open(js_filepath, 'U').read()
  File "/home/psychojoker/code/yunohost/ynh-dev/logilab/cubicweb/ve3/lib/python3.7/codecs.py", line 322, in decode
    (result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x80 in position 653: invalid start byte
make: *** [Makefile:50: js] Error 1

(this one is fixed by modifying the comment in the javascript file)

And if I look at this url https://cubicweb.readthedocs.io/en/default/changes/changelog/#not-yet-released it doesn't contains the latest merged patches so I'm really wondering if it's still being built? So I'm really wondering if the build process isn't broken.

I've also had a lot of warning during doc building but I haven't yet took the time to fix it (and might not depending on priorities.)

Kind regards,

priorityimportant
typebug
done in<not specified>
closed by<not specified>