Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #14022

Re: sysconfig default scheme change in Python 3.10

Show all headers | View raw

On Mon, 28 Mar 2022 at 21:17:40 +0000, Stefano Rivera wrote:
> We've fixed this issue in pybind11 and automake-1.16, so far.

Does this mean that packages that build using Automake, but use the
pregenerated configure/Makefile.in provided by the upstream maintainer
(often on an older or non-Debian distro) instead of regenerating the
build system with dh_autoreconf or equivalent, are going to be broken now?

If true, this will hopefully not affect too many packages, because using
dh_autoreconf is the debhelper default and has been considered a Debian
best-practice for a while; but it seems worth being aware of, because I'm
reasonably sure there are still some packages that deliberately do not
regenerate the build system, and some of those probably build CPython
modules.

    smcv

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

sysconfig default scheme change in Python 3.10 Stefano Rivera <stefanor@debian.org> - 2022-03-28 23:20 +0200
  Re: sysconfig default scheme change in Python 3.10 Simon McVittie <smcv@debian.org> - 2022-03-28 23:50 +0200
    Re: sysconfig default scheme change in Python 3.10 Stefano Rivera <stefanor@debian.org> - 2022-03-29 01:30 +0200

csiph-web