On Thu, Jun 28, 2018 at 11:19 AM, Paul Moore email@example.com wrote:
On 28 June 2018 at 18:45, Bernat Gabor firstname.lastname@example.org wrote:
In the pep it's stated tools can use the tool section https://www.python.org/dev/peps/pep-0518/#id28 and at no point says build tools only. So I don't think at all strange that towncrier uses it. It follows the words of the pep quite rigourously.
The whole PEP is about *build* tools, and in that context, that's what was meant. Maybe the PEP should have been more explicit. Maybe we should have thought about this at the time. Maybe lots of things, but the reality is that we *didn't* intend it to be used for non-build tools, and nevertheless it is being used in that way. We should deal with things as they are now, and not spend ages debating whether things "should" be the way they are.
Oh, I totally imagined that it would be used for non-build tools. I was thinking of stuff like pytest when I wrote that 'tool namespace' section, and of the way all kinds of non-build tools had already colonized setup.cfg (cf. Donald's "paving the cow paths").
It's the One Obvious place for project-specific configuration. That's awesome! Python packaging needs more One Obvious things.