I mostly agree with the design choices.
Based on this, paths ahead:
- Adopt the
toml
library, as guarantees backwards compatibility. - Adopt the
tomli
library as is and use the tomli namespace. - Adopt the
tomli
library under thetoml
id and put it under some namespace (similar to how importlib.metadata is under importlib). There isn’t any good place I see at the moment though.
So I’m personally in favour of 2. Either way, this would likely require a PEP, @hukkinj1 I’m open to writing that up if you co-sign it, probably the least controversial path would be to find a core developer that’s willing to co-maintain the library to also sign-off on it. Perhaps @pf_moore might be willing to help out here.