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

Use poetry_core as build backend #113

Merged
merged 1 commit into from
Feb 16, 2021
Merged

Use poetry_core as build backend #113

merged 1 commit into from
Feb 16, 2021

Conversation

nchepanov
Copy link
Contributor

Closes: #107

According to https://python-poetry.org/docs/pyproject/#poetry-and-pep-517

If your pyproject.toml file still references poetry directly as a build backend,
you should update it to reference poetry_core instead.

According to https://python-poetry.org/docs/pyproject/#poetry-and-pep-517

> If your `pyproject.toml` file still references `poetry` directly as a build backend,
> you should update it to reference poetry_core instead.
@pavdmyt pavdmyt merged commit de2a90a into pavdmyt:master Feb 16, 2021
@pavdmyt
Copy link
Owner

pavdmyt commented Feb 16, 2021

Thanks @nikitos3000 !

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.

Correct pyproject.toml build-backend specification
2 participants