This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients eitan.adler, r.david.murray
Date 2018-05-13.19:03:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1526238222.43.0.682650639539.issue33484@psf.upfronthosting.co.za>
In-reply-to
Content
Yes, we are one of those projects that wants it to be possible to build python without having the tools that generate build artifacts.  You will note that we also check in build artifacts that are produced by our own python scripts, to avoid the problem of trying to build python when you don't yet have a python.

Please use the same version of autotools as were used to generate the current files.  Upgrading autotools is done in a separate PR that only does the upgrade (and I don't know how we decide when to do that...)

Actually, you could just generate the PR with the changes to the source files, not the build artifacte, for the initial review.
History
Date User Action Args
2018-05-13 19:03:42r.david.murraysetrecipients: + r.david.murray, eitan.adler
2018-05-13 19:03:42r.david.murraysetmessageid: <1526238222.43.0.682650639539.issue33484@psf.upfronthosting.co.za>
2018-05-13 19:03:42r.david.murraylinkissue33484 messages
2018-05-13 19:03:42r.david.murraycreate