Skip to content

docs(faq): fix incorrect tools.poetry section name #11150

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.

Sign up for GitHub

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

Merged
Secrus merged 2 commits into from
Oct 21, 2026
Merged

docs(faq): fix incorrect tools.poetry section name #11150

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d54f95c
docs(faq): fix incorrect `tools.poetry` section name
HyperionBurn Oct 18, 2026
0f6cc8c
Merge branch 'main' into docs/fix-tools-poetry-section-name
Secrus Oct 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -273,10 +273,10 @@ Similar to `PIP_REQUESTS_TIMEOUT`, the **experimental** environment variable `PO
can be set to alter this value.


### How do I migrate an existing Poetry project using `tools.poetry` section to use the new `project` section (PEP 621)?
### How do I migrate an existing Poetry project using `tool.poetry` section to use the new `project` section (PEP 621)?

@sourcery-ai sourcery-ai Bot Oct 18, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Medium · Old FAQ links stop working

When a reader follows a saved or external link using the old heading fragment, the corrected heading generates a different fragment, so the browser opens the FAQ page without jumping to the migration answer.

Add an explicit anchor for the old fragment.

Also at docs/faq.md:277.

Prompt for AI agents 
In `docs/faq.md` at line 276:

**Old FAQ links stop working**

When a reader follows a saved or external link using the old heading fragment, the corrected heading generates a different fragment, so the browser opens the FAQ page without jumping to the migration answer.

Add an explicit anchor for the old fragment.

Also at `docs/faq.md:277`.


{{% note %}}
Poetry `>=2.0.0` should seamlessly support both `tools.poetry` section only configuration as well using the `project` section. This
Poetry `>=2.0.0` should seamlessly support both `tool.poetry` section only configuration as well using the `project` section. This
lets you decide when and if you would like to migrate to using the `project` section as [described by PyPA](https://packaging.python.org/en/latest/specifications/pyproject-toml/#declaring-project-metadata-the-project-table).

See documentation on [the `pyproject.toml` file]({{< relref "pyproject" >}}), for information specific to Poetry.
Expand Down Expand Up @@ -432,5 +432,5 @@ build-backend = "poetry.core.masonry.api"
{{% note %}}
- The `classifiers` property is dynamic to allow Poetry to create and manage Python classifiers in accordance with supported Python version.
- The `python` dependency, in this example was replaced with `project.requires-python`. However, note that if you need an upper bound on supported Python versions refer to the documentation [here]({{< relref "pyproject#requires-python" >}}).
- The [`requires-poetry`]({{< relref "pyproject#requires-poetry" >}}) is added to the `tools.poetry` section.
- The [`requires-poetry`]({{< relref "pyproject#requires-poetry" >}}) is added to the `tool.poetry` section.
{{% /note %}}
Loading