4 ms·
Hopefully the role prioritizes blessing existing good practices and creating migration paths and decent interop vs creating new things and pulling an xkcd 927.
by mikepurvis 6y ago
Hopefully the role prioritizes blessing existing good practices and creating migration paths and decent interop vs creating new things and pulling an xkcd 927.
I know everyone's got their favourite thing to be fed up about in the Python packaging ecosystem, but for me it's definitely `setup.cfg` vs `pyproject.toml`.
- di 6y agoHave you seen PEP 621? It sets a standard for putting metadata in `pyproject.toml`. https://www.python.org/dev/peps/pep-0621/ https://www.python.org/dev/peps/pep-0621/
- mikepurvis 6y agoI'm well aware. Have you seen this drama about it? https://github.com/python/mypy/issues/5205#issuecomment-410281336 https://github.com/python/mypy/issues/5205#issuecomment-4102...
- di 6y agoThat comment was made two years before PEP 621 even existed.
- mikepurvis 6y agoOkay, so then maybe my issue is that four years existed between PEP 518 and 621. :|
- sigzero 6y agoThere really isn't any "drama" in that discussion. pyproject.toml is the way forward and projects will need to adopt it at some point.
- amachefe 6y agoProvided both are supported while new projects move to pyproject.toml I really don't like how projects are being broken
- Thorentis 6y agoHappy to see an alternative to json and YAML being used. TOML has been a delight whenever I've used it.
- aitchnyu 6y agoScratching my head, would they do that without a toml parser in std?
- deleted 6y ago[deleted]