On Mon, Oct 8, 2018 at 12:23 PM Nathaniel Smith email@example.com wrote:
On Mon, Oct 8, 2018 at 2:55 AM, Steven D'Aprano firstname.lastname@example.org wrote:
On Mon, Oct 08, 2018 at 09:10:40AM +0200, Jimmy Girardet wrote:
Each tool which wants to use pyproject.toml has to add a toml lib as a conditional or hard dependency.
Since toml is now the standard configuration file format,
It is? Did I miss the memo? Because I've never even heard of TOML before this very moment.
He's referring to PEPs 518 and 517 , which indeed standardize on TOML as a file format for Python package build metadata.
I think moving anything into the stdlib would be premature though – TOML libraries are under active development, and the general trend in the packaging space has been to move things *out* of the stdlib (e.g. there's repeated rumblings about moving distutils out), because the stdlib release cycle doesn't work well for packaging infrastructure.
If I had the energy to argue it I would also argue against using TOML in those PEPs. I personally don't especially care for TOML and what's "obvious" to Tom is not at all obvious to me. I'd rather just stick with YAML or perhaps something even simpler than either one.