> On May 7, 2016, at 5:05 PM, Robert Collins <robe...@robertcollins.net> wrote: > > Either we are defining the long term thing now, in which case that > huge pile of complexity lands on us, and we have to get everything > right. > > Or we are defining a thing which solves the present bug, and as long > as we make sure it does not bind us in future, we're not hamstrung. > > E.g. use setup.cfg now. Add pybuild.toml later. (btw, terrible name, > as pybuild is a thing in the debian space, and this will confuse the > heck out of folk). https://wiki.debian.org/Python/Pybuild
I think this is roughly true, we could either do the simplest thing and just add ``setup_requires`` to ``setup.cfg`` and teach pip how to understand them and then worry about a new format later, or we can do a new format now and add a bit of complexity to what we need to specify (though I don't think _too_ much complexity, we don't have to define the build system stuff now, just make sure we don't back ourselves into a corner with that). I think either answer is OK, just the second one is a bit more work and we might either get the start of a better format _now_ or end up regretting what we pick when we add more things to it. ----------------- Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig