undefined | Better HN

0 pointsbulatb3y ago0 comments

Newer packaging-related PEPs require TOML, and many developer tools use TOML by choice, but a fresh install of Python couldn't actually read it. That required workarounds from tool and library maintainers, making it more complicated to support as many users' preferences and ways of working as possible.

However you prefer to work, your tools may now be easier to test and maintain. This change is good for everyone.

0 comments

mixmastamyk3y ago

Rather unnecessary. See my comment above.

faho3y ago

These files are already in toml, so it's only "unnecessary" if you ask for them to switch the file format.

Otherwise, adding tools to the standard library to read file formats required by the ecosystem is a good idea, regardless of whether you agree with the particular format.

digisign3y ago

They fixed a problem that they created.

History has shown that worrying about an incompatibility with the moribund Python 2 that never affected trivial packaging config was a waste of time.

Meanwhile we still have a setup.cfg on a work project, has worked without issue for 15+ years.

j / k navigate · click thread line to collapse