Support non-multiple and non-named values in Yields and Receives

[the-13th-letter]

This PR fixes #263 by applying the same logic from the Returns section parser to the Yields and Receives parser. The Yields section parser is configured with the same two configuration variables returns_multiple_items and returns_named_value, whereas the Receives section parser is configured via the new receives_multiple_items and receives_named_value configuration variables. Furthermore, the parsing of multiple or single docstring block contents, of named or unnamed parameters, and the unpacking of generator and/or tuple return annotations has been refactored into separate functions.

---

Contents:

• 8a78e68 duplicates the non-multiple return and the named value parsing support for the Yields and Receives section parsers, essentially via copy-and-paste. Includes suitable tests, based on the Returns section tests.
• 756118f implements the aforementioned refactored functions. This commit is functionally optional, but hopefully useful with respect to future ease of maintenance.
• e01447a fixes linting errors.
• 8e7cb30 adds documentation for the above features.

[the-13th-letter]

Concerning code style, I come from a black/ruff environment, and found no settings in your code repository. So my formatting and linting may be off.

EDIT: nevermind, your CI setup told me where to find the config settings, and what linting errors to fix.

[pawamoy]

Thanks a lot! I appreciate the effort on splitting commits to ease review 🙂

[pawamoy]

Thanks for the update.

Honestly I feel like the "aspect" check is overkill, I'd just prefer we remove it as well as the enum 🙂

[the-13th-letter]

GitHub doesn't seem to recognize a PR that has been reset to an earlier, already-reviewed state as already reviewed…

Also, there's an apparently unrelated, failing CI test on Py3.13/Ubuntu-lowest-direct that's been haunting this PR since its inception.

[pawamoy]

Don't mind the 3.13-lowest failure, it's unrelated indeed and it's allowed to fail.

[pawamoy]

Concerning code style, I come from a black/ruff environment, and found no settings in your code repository. So my formatting and linting may be off.

Just saw this, sorry. There's a make vscode command you can use to configure VSCode for the project 🙂 It overrides local files. It's optional, you can run make format and make check anyway to format code and check it.

[pawamoy]

Erm sorry I pushed a dirty commit. Let me rebase locally and force-push then merge.

[pawamoy]

Thanks again!

[pawamoy]

I refactored the logic again in a80bd3c, I think it's even more readable now.

[the-13th-letter]

That's fine. I wasn't sure if I should touch the "where is the annotation looked up in?" part, so my version doesn't quite reap the same readability benefits as yours.