Skip to content

GH-137623: Use an AC decorator for docstring line length enforcement #137690

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

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

AA-Turner
Copy link
Member

@AA-Turner AA-Turner commented Aug 12, 2025

After thinking about it, @serhiy-storchaka's suggestion to use a decorator seems a better approach. It keeps the information localised to where the problem is, rather than hiding it in libclinic, which most contributors shouldn't need to worry about.

Opening as draft to avoid review-request spam until ready for merge.

A

@AA-Turner AA-Turner force-pushed the clinic/overlong-docstrings-deco branch from fbb070c to 37dbdf7 Compare August 12, 2025 21:15
@skirpichev
Copy link
Contributor

I'm not sure if this is a good approach. It's much harder to get list of exceptions.

rather than hiding it in libclinic, which most contributors shouldn't need to worry about.

You could document this list in the devguide, right?

@AA-Turner
Copy link
Member Author

It's much harder to get list of exceptions.

What are the use-cases for getting the list of too-long docstrings? If we are fixing/improving the docstrings, it could be better to remove a decorator in the same part of the same file, rather than looking in a random different file.

A

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

Successfully merging this pull request may close these issues.

2 participants