Seeking a consensus about the purpose and future of `pyproject.toml`

But the agenda for what exactly? Why do you even feel there’s a need to get a “consensus about the purpose and future of pyproject.toml”? Personally, I don’t care much about pyproject.toml. It’s a file, with some configuration in it. What matters to me is tools. They can put their configuration wherever they like. Certainly, some level of consistency and interoperability is important[1], but what matters more is the user experience for someone trying to write and share code in Python.

I’d rather see a discussion about tools than about pyproject.toml. But much better than either, I’d rather see people developing tools instead of talking about them. We can standardise later, once the tools have established there’s a benefit to be had from a feature, and there’s something worth defining a common structure for.


  1. As the standing delegate for interoperability PEPs, I’d better think interoperability is important :slightly_smiling_face: ↩︎

5 Likes