Dear Engelbert, dear Docutils developers,
On 2023-05-09, engelbert gruber wrote:
> after the quiet test period, 0.20 is the new release
Thank you for the release, it allows closing a number of issues.
It looks like we need fixup release next week.
There are some new issues and glitches (nothing serious yet):
https://sourceforge.net/p/docutils/bugs/461/
Spurious files in the sdist:
docutils.egg-info/SOURCES.html
docutils.egg-info/dependency_links.html
docutils.egg-info/top_level.html
artifacts from the documentation generation?
Should be solved by [r9288] and [r9380]
but we should check the generated sdist before uploading.
https://sourceforge.net/p/docutils/bugs/467/
Include tox.ini in the sdist.
Should be fixed with [r9379]
We should check the generated sdist before uploading.
https://sourceforge.net/p/docutils/bugs/470/
Test failures with Pygments 2.13.x
We need to check the results for Docutils 0.20 and Pygments 2.13 (and
possibly just skip the tests if the Pygments version is 2.13) because
from the proposed patch it seems that 2.13 introduced a change to
whitespace handling that was superseded in 2.14 with a different
change.
https://sourceforge.net/p/docutils/bugs/471/
A "false alarm" when testing with pypy3.
Requires special casing in the expeced error output
(we need a suitable conditional to tell whether the test run under pypy).
More spurious files in the docutils-0.20.tar.gz sdist package:
TODO.txt
a local file not in the repo (there is "docs/dev/todo.txt")
(consistent formatting in HISTORY.txt is nice to have
but a minor issue for changes from years ago).
manpage-URUE.txt
math.txt
mwe-test.txt
Left-overs from local testing?
Maybe move manpage examples to test/functional/input/...
(math.txt is already there and also used in the functional tests).
There is also a MANIFEST file in docutils-0.20.tar.gz while
in my locally generated sdist, there is only MANIFEST.in
I don't know whether MANIFEST is actually required or spurious
in an sdist.
Thanks,
Günter
|
