On Thu, Sep 28, 2017 at 8:46 AM, xoviat <xoviat@gmail.com> wrote:

No. Setuptools is what projects without a build_backend in pyproject.toml get. Not distutils. We should make it clear now that the distutils namespace belongs to setuptools except for when building cpython.

On Sep 27, 2017 2:33 PM, "Ned Deily" <nad@python.org> wrote:
On Sep 27, 2017, at 13:31, Steve Dower <steve.dower@python.org> wrote:
> setuptools is totally welcome in my book to simply copy the compiler infrastructure we already have from core and never look back. It really does need to be maintained separately from CPython, especially on Windows where we continue to get innovation in the targeted tools. I know it's a big ask, and it's one that I can't personally commit real time to (though I obviously will as much as possible), but I do think it is necessary for our ecosystem to not be tied to CPython release cycles.

Whatever is done, keep in mind that currently distutils is required to build Python itself, e.g. the standard library. And that at least one important project, numpy, already subclasses distutils.

For numpy that seems fixable (if it even breaks, it may not). As long as the setuptools maintainers are willing to keep numpy.distutils compatibility, I'm happy to make the necessary changes in numpy.

FYI, it has happened twice (IIRC) in the last five years that a new setuptools release broke numpy.distutils. This was fixed very quickly with good collaboration between the projects.

Ralf

--
Ned Deily
nad@python.org -- []

_______________________________________________
Distutils-SIG maillist - Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig

_______________________________________________
Distutils-SIG maillist - Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig