The suspicious check is still executed as part of the release process and release managers have been
lately fixing some actual errors that the suspicious target can find. For this reason, reactivate the suspicious
until we decide what to do in a coordinated fashion.
- name: 'Install build dependencies'
run: make -C Doc/ PYTHON=../python venv
- name: 'Build documentation'
- run: xvfb-run make -C Doc/ PYTHON=../python SPHINXOPTS="-q -W --keep-going -j4" doctest html
+ run: xvfb-run make -C Doc/ PYTHON=../python SPHINXOPTS="-q -W --keep-going -j4" doctest html suspicious
- name: 'Upload'
uses: actions/upload-artifact@v2.2.2
with:
- cd Doc
- make venv PYTHON=python
script:
- - make check html SPHINXOPTS="-q -W -j4"
+ - make check html suspicious SPHINXOPTS="-q -W -j4"
- name: "Documentation tests"
os: linux
language: c
Set by the :envvar:`PYTHONPLATLIBDIR` environment variable.
Default: value of the ``PLATLIBDIR`` macro which is set by the
- :option`configure --with-platlibdir option <--with-platlibdir>` (default:
+ :option:`configure --with-platlibdir option <--with-platlibdir>` (default:
``"lib"``).
Part of the :ref:`Python Path Configuration <init-path-config>` input.
library/importlib.metadata,,:main,"EntryPoint(name='wheel', value='wheel.cli:main', group='console_scripts')"
library/importlib.metadata,,`,loading the metadata for packages for the indicated ``context``.
library/re,,`,"`"
+using/configure,84,:db2,=db1:db2:...