[aclark4life]

PYTHON-6263

Changes in this PR

• Removes the blacken-docs hook from .pre-commit-config.yaml.
• Removes the now dead blacken-docs:off/on skip markers from CODING-STANDARDS.md.

The hook formatted code samples in docs with the pinned black 22.3.0 while the repo formatter is ruff, and it failed the static job on #3131 by rewriting CONTRIBUTING.md.

Test Plan

• uvx pre-commit run --all-files --hook-stage manual passes.

Checklist

Checklist for Author

• Did you update the changelog (if necessary)?
• Is the intention of the code captured in relevant tests?
• If there are new TODOs, has a related JIRA ticket been created?

Checklist for Reviewer

• Does the title of the PR reference a JIRA Ticket?
• Do you fully understand the implementation? (Would you be comfortable explaining how this code works to someone else?)
• Have you checked for spelling & grammar errors?
• Is all relevant documentation (README or docstring) updated?

[Copilot]

🟢 Approval recommended

No active review issues block the removal of the documentation-formatting hook and obsolete skip markers.

No open issues 🎉

What changed in this PR

Removes the documentation-formatting hook that used pinned Black 22.3.0 alongside the repository’s Ruff formatter, addressing the unwanted documentation rewrites reported in #3131.

Changes:

• Removes the blacken-docs pre-commit hook and its Black dependency.
• Removes obsolete skip-marker comments from the coding standards without changing the guidance.

File	Description
CODING-STANDARDS.md	Removes the unused blacken-docs:off/on comments.
.pre-commit-config.yaml	Removes the blacken-docs hook and pinned Black dependency.

_{Review effort: Balanced}

[NoahStapp]

We should turn on ruff's markdown code formatting and docstring formatting if we remove blacken-docs. It'll probably cause some formatting changes but we still want full linting coverage.

[NoahStapp]

See comment above.

[aclark4life]

We should turn on ruff's markdown code formatting and docstring formatting if we remove blacken-docs. It'll probably cause some formatting changes but we still want full linting coverage.

We should, but I'm not sure that it should be done in this PR, because the replacement is not equivalent to what it replaces:

• blacken-docs formatted code blocks and left doctest structure alone. docstring-code-format deletes the bare ... continuation markers and injects blank lines inside doctest examples. That changes how the doctest job parses those examples so code that passed before can fail after.
• We have 22 files of doctest examples that CI executes so the formatter's edits are not cosmetic. Verifying means running the doctest job and reviewing and fixing each diff.
• The diff also rewrites user-facing examples ({'$match': ...} becomes {"$match": ...}) so it drags review of rendered docs into a config PR.

If we do everything in this PR and the doctest job fails after the PR merges the fix is to disable docstring-code-format, but the reformatting commit and the hook removal are in the same branch so reverting the branch also brings blacken-docs back! Separate PRs let you revert the formatting without undoing the hook removal.

[NoahStapp]

We should turn on ruff's markdown code formatting and docstring formatting if we remove blacken-docs. It'll probably cause some formatting changes but we still want full linting coverage.

We should, but I'm not sure that it should be done in this PR, because the replacement is not equivalent to what it replaces:

* `blacken-docs` formatted code blocks and left doctest structure alone. `docstring-code-format` deletes the bare `...` continuation markers and injects blank lines inside doctest examples. That changes how the doctest job parses those examples so code that passed before can fail after.

* We have 22 files of doctest examples that CI executes so the formatter's edits are not cosmetic. Verifying means running the doctest job and reviewing and fixing each diff.

* The diff also rewrites user-facing examples `({'$match': ...} becomes {"$match": ...})` so it drags review of rendered docs into a config PR.

If we do everything in this PR and the doctest job fails after the PR merges the fix is to disable docstring-code-format, but the reformatting commit and the hook removal are in the same branch so reverting the branch also brings blacken-docs back! Separate PRs let you revert the formatting without undoing the hook removal.

Sounds good, can you open a follow-up ticket to turn on ruff's formatting?