Re: [Docutils-develop] docutils prerelease 0.19b1

[Adam T. <aat...@ou...>]

Dear Günter,

> Another idea would be opening tickets at major contributing projects (MyST, furo or other CSS schemes, ...) and ask for testing with Docutils 0.19b there.

I opened several:

- Sphinx (covered by me)
- https://github.com/getnikola/nikola/issues/3632
- https://github.com/getpelican/pelican/issues/3017
- https://github.com/executablebooks/MyST-Parser/issues/591
- https://github.com/brechtm/rinohtype/issues/340

Themes:

- https://github.com/pydata/pydata-sphinx-theme/issues/757
- https://github.com/mgeier/insipid-sphinx-theme/issues/101
- https://github.com/pradyunsg/furo/issues/462
- https://github.com/executablebooks/sphinx-book-theme/issues/578
- https://github.com/jbms/sphinx-immaterial/issues/113

> Could you also have a look, if there are DeprecationWarnings when compiling a project?

> I could successfully compile "PyLit" documentation with sphinx-build
> 3.4.3 (from Debian/stable) and Docutils 0.19b (with warnings because of
> the "meta" element changes, but the result looks fine (although not
> polished yet, see https://milde.codeberg.page/PyLit/).

Sorry, I don't understand -- deprecation warnings from Docutils or from Sphinx? Do you mean expected warnings that we added or unexpected ones? Happy to test, my time during weekdays is limited at the moment though.

Thanks,
Adam