On Tue, Nov 2, 2021 at 1:12 PM Khem Raj wrote:
> On Tue, Nov 2, 2021 at 1:06 PM Ross Burton wrote:
> >
> > On Tue, 2 Nov 2021 at 18:06, Khem Raj wrote:
> > > So shouldn’t we fix python3-config to not use distutils and switch to
> setup tools instead ?
> > >
> > > I am afraid that masking the wa
On Tue, Nov 2, 2021 at 1:06 PM Ross Burton wrote:
>
> On Tue, 2 Nov 2021 at 18:06, Khem Raj wrote:
> > So shouldn’t we fix python3-config to not use distutils and switch to setup
> > tools instead ?
> >
> > I am afraid that masking the warning will come biting soon when this is
> > turned into
On Tue, 2 Nov 2021 at 18:06, Khem Raj wrote:
> So shouldn’t we fix python3-config to not use distutils and switch to setup
> tools instead ?
>
> I am afraid that masking the warning will come biting soon when this is
> turned into a hard error
That is a much bigger question that needs to be don
On Tue, Nov 2, 2021 at 11:02 AM Ross Burton wrote:
> Our patched python3-config uses distutils, but that will emit a
> DeprecationWarning when imported. This isn't useful when using the
> output of python3-config to find include paths.
So shouldn’t we fix python3-config to not use distutils an
Our patched python3-config uses distutils, but that will emit a
DeprecationWarning when imported. This isn't useful when using the
output of python3-config to find include paths.
This isn't a huge problem typically as the warning goes to stderr, but
some build systems read both stdout and stderr.
