4 ms·
Please don't do this. It's just yet another tool which makes the same thing as setup.py yet another way with no real benefit and it's not "standard". Everyone w
by Walkman 9y ago
Please don't do this. It's just yet another tool which makes the same thing as setup.py yet another way with no real benefit and it's not "standard". Everyone who did some Python packaging already know at least the basics of setup.py, now they all should learn yet another file type syntax for the same problem.
- atarian 9y ago> now they all should learn yet another file type syntax for the same problem Are you really implying that learning INI would be a burden?
- Walkman 9y agoYes. Obviously it doesn't seem like so at the first glance, but when you have a product like ours, where there are hundreds of small things like this, it can really add up. I believe that everyone should use and improve the same, standard tools so we can have few, but high quality things. When you come up with something new which is just slightly different from the existing one (see Python3 first versions...) I think you are doing the wrong thing.
- sciyoshi 9y agoNewer versions of setuptools have builtin support for more fields in setup.cfg: http://setuptools.readthedocs.io/en/latest/setuptools.html#configuring-setup-using-setup-cfg-files http://setuptools.readthedocs.io/en/latest/setuptools.html#c... That along with setuptools-scm and pip-tools have for me solved most of the issues that pbr addresses.