This is the mail archive of the mailing list for the glibc project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Ping^2 Re: Use to generate ulps table for manual

On Mon, Oct 1, 2018 at 11:21 AM Carlos O'Donell <> wrote:
> On 10/1/18 11:06 AM, Joseph Myers wrote:
> > On Tue, 25 Sep 2018, Joseph Myers wrote:
> >> Ping.  Any conclusion on this question about indirect dependencies
> >> introduced by use of Python?
> >
> > Another ping on this question....
>  Could you help me to gather consensus?
> If you could write up the following:
> * Exact version of python to use.
> * Exact set of imports we need.
> I'll take that and try to get an acknowledgment from each of the
> distributions. I'll email all the maintainers and follow up with
> them (all on libc-alpha) in a new thread starting with the information
> you will put together for me.
> I'll also include some of the resolution about the concerns regarding
> building python on an old distribution.

For the record, although I offered some details earlier about how
Debian packages Python, I have no official relationship to Debian and
cannot speak for any of their teams that might care about this
proposed change.

As a glibc developer who might well take on some of the work of
rewriting existing build logic in Python, I would like to put in a
word for requiring Python 3.(>=4) rather than allowing 2.7 as well.
The 2.x series is close to end-of-life, writing scripts that work with
both major versions of the language is significantly harder than
writing 3.x-only code, and I fear 2.x build compatibility will not be
adequately tested.  3.4 is the oldest version of the 3.x series still
in wide use AFAIK.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]