On Wed, 2025-03-26 at 09:37 +0100, Ulrich Müller wrote: > > > > > > On Wed, 26 Mar 2025, Michał Górny wrote: > > > On Wed, 2025-03-26 at 09:27 +0100, Ulrich Müller wrote: > > > > > > > > On Tue, 25 Mar 2025, Michał Górny wrote: > > > > > > > 5. We now make it easier to override the PEP517 backend used. You set > > > > DISTUTILS_UPSTREAM_PEP517 to the backend used upstream, and > > > > DISTUTILS_USE_PEP517 to the backend you want to use -- and you don't > > > > have to edit build-backend in pyproject.toml anymore. Most packages > > > > won't need it, and should just continue setting DISTUTILS_USE_PEP517. > > > > > > These variable names confuse me since some time. How are they related to > > > distutils? > > > The eclass is called 'distutils-r1', so 'distutils' is the namespace for > > all variables and functions. > > Then let me rephrase the question, why is the eclass called > distutils-r1? How is it related to distutils?
It is called distutils-r1 because it is a logical continuation of distutils.eclass which was named this way back in 2002, when its primary function was dealing with the distutils build system. -- Best regards, Michał Górny
signature.asc
Description: This is a digitally signed message part
