Skip to content
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.

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

fix: improve detection of poetry 2 projects #274

Merged
merged 1 commit into from
Jan 26, 2025
Merged

Conversation

nat-n
Copy link
Owner

@nat-n nat-n commented Jan 26, 2025

Projects created with poetry >= 2.0 don't necessarily include a tool.poetry
table in the pyproject.toml. Thus poethepoet cannot rely on the presence or
absence of this table to tell whether it is appropriate to default to using
the PoetryExecutor to run tasks with poetry's venv.

It seems the best remaining indicator is the content of the build-system which
poetry still configures consistently, although this is less ideal.

Projects created with poetry >= 2.0 don't necessarily include a
tool.poetry table in the pyproject.toml. Thus poethepoet cannot
rely on the presence or absence of this table to tell whether
it is appropriate to default to using the PoetryExecutor to run
tasks with poetry's venv.

It seems the best remaining indicator is the content of the
build-system which poetry still configures consistently, although
this is less ideal.
@nat-n nat-n merged commit b3b6df5 into development Jan 26, 2025
20 checks passed
@nat-n nat-n deleted the poetry_detection branch January 26, 2025 19:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant