Description

Followup to #10742

We use Ruff to enforce docsting style

We follow pep257 style (http://www.pydocstyle.org/en/stable/error_codes.html) for checks.

Currently, we ignore the following rules and should work towards enabling them:

Missing Docstrings

• D100 | Missing docstring in public module Add some context comments to pyproject.toml #40741
• D102 | Missing docstring in public method https://lists.apache.org/thread/lcvocwxnrrzq9ofrg4b4hj0yvpzbnygf
• D103| Missing docstring in public function https://lists.apache.org/thread/lcvocwxnrrzq9ofrg4b4hj0yvpzbnygf
• D104 | Missing docstring in public package Add some context comments to pyproject.toml #40741
• D107 | Missing docstring in __init__ https://lists.apache.org/thread/lcvocwxnrrzq9ofrg4b4hj0yvpzbnygf
• D214 | Consistent multi-line docstring indentation
• D215 | Enforce number of underscores if you use underlines in a multi-line docstring
• PT004 | Fixture does not return anything, add leading underscore
• PT006 | @pytest.mark.parametrize names should be a tuple
• PT007 | @pytest.mark.parametrize values should be a tuple
• PT011 | pytest.raises() is too broad, set the match parameter
• TCH003 | stdlib imports which are only used for typechecking go in to TYPE_CHECKING block

It would be good if we can enable them one by one -- separate PRs are ok

Rough process to fix these

0. Set up your dev environment [docs]
   0.5. Go to your airflow directory and run ruff check. Write down the number of failures. Mine currently says 8. This step is just to make sure it's working and give you a baseline.

1. Open /airflow/pyproject.toml

2. In the ignore list (currently starting on line 301) comment out the rule you intend to work on

3. In a terminal, go to the airflow directory and run ruff check again. It should now fail with WAY more errors. Mine currently says 863. If the number didn't go way up, something is wrong with your setup.

4. Have a quick scroll through that list, paying attention to which ones failed because of the rule you just enabled.

5. Come up with a rough plan to break that down into bites. Maybe pick one directory that has a bunch of failures and start fixing there.

6. After you have a handful of fixes done: remove your comment (so it is ignored again) and submit a PR with that chunk of changes (see the Contributing docs in step 0)

PLEASE submit these in many small PRs. If you do it all at once it will turn into a 3000-line PR and nobody will review it. Eventually, on the last chunk you'll just remove that line from the ignore list entirely when there are no more violations to fix.

Let me know if you need any help, or ask in the Slack server.