Closed Bug 1553638 Opened 5 years ago Closed 5 years ago

[wpt-sync] Sync PR 16960 - Update sphinx to 2.0.1

Categories

(Testing :: web-platform-tests, defect, P4)

defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 16960 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/16960
Details from upstream follow.

pyup-bot <github-bot@pyup.io> wrote:

Update sphinx to 2.0.1

This PR updates Sphinx from 1.8.5 to 2.0.1.

<details>
<summary>Changelog</summary>

### 2.0.1
```
==============================

Dependencies

Incompatible changes

Deprecated

Features added

Bugs fixed

  • LaTeX: some system labels are not translated

  • RemovedInSphinx30Warning is marked as pending

  • deprecation warnings are not emitted

    • sphinx.application.CONFIG_FILENAME
    • sphinx.builders.htmlhelp
    • :confval:viewcode_import
  • 6208: C++, properly parse full xrefs that happen to have a short xref as prefix.

  • 6220, 6225: napoleon: AttributeError is raised for raised section having
    references

  • 6245: circular import error on importing SerializingHTMLBuilder

  • 6243: LaTeX: 'releasename' setting for latex_elements is ignored

  • 6244: html: Search function is broken with 3rd party themes

  • 6263: html: HTML5Translator crashed with invalid field node

  • 6262: html theme: The style of field lists has changed in bizstyle theme

Testing

```



### 2.0.0
```
* 6196: py domain: unexpected prefix is generated

Testing

```



### 2.0.0b2
```
* Add a helper function: ``sphinx.testing.restructuredtext.parse()``
```



### 2.0.0b1
```
* Stop to use ``SPHINX_TEST_TEMPDIR`` envvar
```

</details>

<details>
<summary>Links</summary>

Whiteboard: [wptsync downstream] → [wptsync downstream error]
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
Whiteboard: [wptsync downstream error] → [wptsync downstream]
You need to log in before you can comment on or make changes to this bug.