Merged
Conversation
As docformatter becomes more strict in identifying patterns and handling the various patterns that are identified, some of the older tests are failing. These tests fail because the patterns in the test strings are not strictly reST, Sphinx, etc.
dotlambda
referenced
this pull request
in NixOS/nixpkgs
Sep 9, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Address most of the issues reported in #321. A new release/v1.7.8 branch will be created for testing the release candidate and tracking the fixes to issues identified rather than using a release candidate tag. The tag causes pre-commit autoupdate to use potentially buggy code which is not the preferred approach for me as it causes unnecessary heartache for user who choose not to participate in testing.