docs: show PEP 735 dependency-groups in README

[srikaaviya]

Fixes #10548.

Updates the README example to use the standardized PEP 735
[dependency-groups] table instead of [tool.poetry.group.*.dependencies],
keeping Poetry-specific settings as-is.

Summary by Sourcery

Documentation:

• Refresh README dependency group examples to use the PEP 735 [dependency-groups] table while keeping Poetry-specific settings unchanged.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the README dependency group example to use standardized PEP 735 [dependency-groups] syntax instead of Poetry-specific [tool.poetry.group.*.dependencies] tables while preserving the conceptual explanation of dev/docs groups and selective installation.

File-Level Changes

Change	Details	Files
Update README dependency group configuration example from Poetry-specific tables to PEP 735 [dependency-groups] syntax.	Replace [tool.poetry.group.dev.dependencies] dev group example with a [dependency-groups] section containing a dev group list of pytest-related dependencies using version ranges instead of caret constraints. Replace docs group example using [tool.poetry.group.docs] and [tool.poetry.group.docs.dependencies] with a docs entry under [dependency-groups] using an equivalent Sphinx version range. Adjust surrounding comments to reference PEP 735 and keep the explanation about explicit installation of docs dependencies.	README.md

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#10548	Update the README example to show PEP 735 [dependency-groups] usage instead of [tool.poetry.group.*.dependencies] where appropriate.	✅

Possibly linked issues

• Showing dependency-groups in README #10548: The PR updates README dependency group examples to the PEP 735 [dependency-groups] syntax requested in the issue.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've left some high level feedback:

• The comment via 'poetry install --with docs' is still Poetry-specific while the example now uses PEP 735 [dependency-groups]; consider either clarifying that this command is Poetry-specific or updating the example/command so they match the same tooling context.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The comment `via 'poetry install --with docs'` is still Poetry-specific while the example now uses PEP 735 `[dependency-groups]`; consider either clarifying that this command is Poetry-specific or updating the example/command so they match the same tooling context.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}