Skip to content

Correct statement on PEP-518 #1482

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

Closed
wants to merge 2 commits into from
Closed

Correct statement on PEP-518 #1482

wants to merge 2 commits into from

Conversation

nuno-andre
Copy link

As explicitly stated in PEP-518:

Tools should not require the existence of the [build-system] table. A pyproject.toml file may be used to store configuration details other than build-related data and thus lack a [build-system] table legitimately. It is up to the tool to decide how to handle this case.

Also removed (if you want to avoid an extra file) since is not uncommon for a pyproject.toml to have the configuration of a single tool that otherwise would have its own file.

As explicitly stated in [PEP-518](https://www.python.org/dev/peps/pep-0518/#build-system-table):

> _Tools should not require the existence of the `[build-system]` table. A `pyproject.toml` file may be used to store configuration details other than build-related data and thus lack a `[build-system]` table legitimately. It is up to the tool to decide how to handle this case._

Also removed _(if you want to avoid an extra file)_ since is not uncommon for a `pyproject.toml` to have the configuration of a single tool that otherwise would have its own file.
@gaborbernat
Copy link
Member

I don't think tox follows that advise, or pip for that matter. I'm pretty sure everything would break without it. Furthermore tox is encouraging best practices, and having the build part defined is definitely encouraged and best practice. So I think the current statement is the good one.

@asottile
Copy link
Contributor

asottile commented Dec 7, 2019

I'm -1 as well, the claim that pyproject.toml is "the standard for Python tools" simply isn't correct. It is a specced standard for build tools yes, but that doesn't mean every python tool must put their configuration there

@di
Copy link

di commented May 31, 2022

I think this should probably be revisited, I filed #2429 to start a new conversation.

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.

4 participants