Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docutils 0.21.2 breaks the test suite #310

Closed
kurtmckee opened this issue Jun 27, 2024 · 4 comments · Fixed by #315
Closed

docutils 0.21.2 breaks the test suite #310

kurtmckee opened this issue Jun 27, 2024 · 4 comments · Fixed by #315
Labels

Comments

@kurtmckee
Copy link
Contributor

kurtmckee commented Jun 27, 2024

docutils 0.20.1, installed in the Python 3.8 tox environment, matches test suite expectations.

docutils 0.21.2, installed in Python 3.9+ tox environments, breaks the test suite.

There appear to be small changes, like additional newlines, but also substantial differences, like this partial diff between what the test suite expected and what docutils 0.21.2 emitted:

- <nav class="contents" id="contents">\n<p class="topic-title">Contents</p>
+ <nav class="contents" id="contents">\n<p class="topic-title"><a href="#top" rel="nofollow">Contents</a></p>

As this isn't simply a whitespace change, I'm not currently pursuing a solution to this.

kurtmckee added a commit to kurtmckee/pr-pypa-readme_renderer that referenced this issue Jun 28, 2024
@miketheman miketheman added the bug label Jun 29, 2024
@miketheman
Copy link
Member

Thanks for figuring that out.

While pinning to the older version will help pass the test suite, if we don't pin an upper bound to the package's dependency we'll get a different result from rendering the output (which might already be happening to folks today).

I think I'm more amenable to pushing forward with using the latest (and bumping the minimum version in pyproject.toml) and adapting the tests.

Python 3.8 EOL is in 4 months, I don't feel strongly that we need to preserve support for this library going forward.

@kurtmckee
Copy link
Contributor Author

@miketheman Thanks for the feedback. To confirm, #311 could be closed in favor of a PR that:

  • Drops support for Python 3.8
  • Pins docutils to 0.21.x
  • Updates the fixture files that render differently under the new docutils version

Does that match what you would expect from a PR that could close this issue?

@miketheman
Copy link
Member

Yes, that seems to be a good list of items.
When dropping 3.8 support, please also update the classifier list.

@kurtmckee
Copy link
Contributor Author

@miketheman I opened #315 based on this feedback. If that PR looks good then #311 can be summarily closed. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants