Isn't it neat that pip-installable packages can be built without distutils?
What else can we do to make the experience better for those who would try to replace distutils?
On 31 Mar 2015 04:11, "Donald Stufft" <donald@stufft.io> wrote:
One of the other key missing pieces is a tool independent regression test suite that defines the expected setup.py CLI. The existing setuptools, distutils & distutils2 test suites do a lot of their testing via Python level APIs rather than being written as external functional tests for the setup.py CLI they provide. So one place to start would be to work on creating such an independent test suite (from a technical perspective, I'd suggest basing it on pytest & tox), focusing initially on the commands that pip invokes, and using the pip/virtualenv/setuptools/distutils/distutils2 test suites as guides for options and environment variable settings to check. After that, figuring out how to scan the Debian & Fedora repos to extract the distro level build commands used for various projects would provide an additional source of good test suite fodder. The advantage of such a test suite project is that it would start to meaningfully quantify what "replacing distutils" actually means from the practical perspective of "calling setup.py at the command line". Regards, Nick.
participants (3)
-
Daniel Holth
-
Donald Stufft
-
Nick Coghlan