regen autotools related files

[grimreaper]

BPO	33486
Nosy	@malemburg, @gvanrossum, @warsaw, @birkenfeld, @benjaminp, @tarekziade, @ned-deily, @merwok, @encukou, @serhiy-storchaka, @grimreaper, @matrixise
PRs	bpo-33486: regen autotools related files #6783 bpo-33486: regen autotools files using autoupdate+autoreconf #6853

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = None
created_at = <Date 2018-05-13.19:08:03.281>
labels = ['3.8', 'type-feature', '3.7', 'build']
title = 'regen autotools related files'
updated_at = <Date 2018-11-04.19:43:41.906>
user = 'https://github.com/grimreaper'

bugs.python.org fields:

activity = <Date 2018-11-04.19:43:41.906>
actor = 'ned.deily'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Build']
creation = <Date 2018-05-13.19:08:03.281>
creator = 'eitan.adler'
dependencies = []
files = []
hgrepos = []
issue_num = 33486
keywords = ['patch']
message_count = 7.0
messages = ['316477', '316625', '316629', '325411', '325412', '329249', '329250']
nosy_count = 13.0
nosy_names = ['lemburg', 'gvanrossum', 'barry', 'anthonybaxter', 'georg.brandl', 'benjamin.peterson', 'tarek', 'ned.deily', 'eric.araujo', 'petr.viktorin', 'serhiy.storchaka', 'eitan.adler', 'matrixise']
pr_nums = ['6783', '6853']
priority = 'normal'
resolution = None
stage = 'commit review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue33486'
versions = ['Python 2.7', 'Python 3.6', 'Python 3.7', 'Python 3.8']

[grimreaper]

There are few if any functional changes, but this is helpful when making other changes to the build system.

[serhiy-storchaka]

If these changes are autogenerated, I would prefer that a trusted core developer create a PR.

Is it safe to bump the minimal required version of autotools to 2.69? This can prevent building Python on conservative systems.

[grimreaper]

If these changes are autogenerated, I would prefer that a trusted core developer create a PR.

They are fully auto-generated (using autoupdate and autoreconf). It someone else wants to submit the PR, feel free.

Is it safe to bump the minimal required version of autotools to 2.69? This can prevent building Python on conservative systems.

This should only affect rerunning autoreconf and related tools. It won't affect the use of "configure" (and therefore "make") which is checked into the repository.

[encukou]

If these changes are autogenerated, I would prefer that a trusted core developer create a PR.

I got the same changes in configure.ac.

[encukou]

New changeset 24f6846 by Petr Viktorin (Eitan Adler) in branch 'master':
bpo-33486: regen autotools files using autoupdate+autoreconf (GH-6853)
24f6846

[ned-deily]

If we are going to bump the tools version from 2.65 to 2.69 for master, we should probably bump them for all active branches. It creates confusion and makes backporting more difficult. Besides, it appears that, at the moment, the checked-in configure files for 3.7, 3.6, and 2.7 were all generated with 2.69 anyway :) if doing so, the reference to 2.65 in the devguide setup.rst should also be updated.

[matrixise]

Hi Ned, thanks for this clarification