You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using sphinx-pyproject on a project setup with Poetry results in the following error:
dom_toml.parser.BadConfigError: No 'project' table found in .../pyproject.toml
Indeed the project metadata are stored in the [tool.poetry] table, instead of project.
I wonder whether it would be possible to support Poetry's setup by providing a project_table optional parameter defaulting to project which Poetry users could override to tool.poetry?
The text was updated successfully, but these errors were encountered:
[tool.poetry]
name = "example"version = "0.1.0"authors = [
"Your Name <you@domain.com>",
]
description = "some description"
Relevant poetry issue python-poetry/poetry#3332
I think it's better to wait for changes in poetry and duplicate tables in pyproject.toml as a workaround.
I'll happily accept a PR adding support for poetry support, if poetry supporting PEP 621 is a way off.
What's required is a different version of the ProjectParser class that parses from [tool.poetry] instead of [project], and a bit of logic in SphinxConfig.__init__ to decide on which table and class to use.
Using
sphinx-pyproject
on a project setup with Poetry results in the following error:dom_toml.parser.BadConfigError: No 'project' table found in .../pyproject.toml
Indeed the project metadata are stored in the
[tool.poetry]
table, instead ofproject
.I wonder whether it would be possible to support Poetry's setup by providing a
project_table
optional parameter defaulting toproject
which Poetry users could override totool.poetry
?The text was updated successfully, but these errors were encountered: